RFP Amendment 2.docx

Steve Sisolak

State of Nevada Department of Administration Purchasing Division 515 E. Musser Street, Suite 300 Carson City, NV 89701

Peter Long

Governor

Acting Director

Kevin D. Doty

Administrator

The following shall be a part of RFP # 05TO-S953. If a vendor has already returned a proposal and any of the information provided below changes that proposal, please submit the changes along with this amendment. You need not re-submit an entire proposal prior to the opening date and time.

First Questions and Responses to RFP:

1. Technical Requirements - System Interfaces: Can you share more information related to the various State systems and databases (in addition to the Taxation payment processing system) which the proposed solution will need to connect? Primarily interested in technical requirements. Would state see value in platform collecting tax data and option for taxes to be collected upon each consumer transaction and submitted to a state bank account within days of every transaction within the state?

It will not be necessary for the chosen system to include tax collections simultaneous to a transaction, nor will it need to connect to any state systems for the duration of the Pilot Program. The State envisions the chosen system to collect data relative to each transaction, which will include sufficient information in calculating the appropriate taxes. The process for the collection of tax dollars will remain substantially similar to the current process for the duration of the Pilot Program.

2. Timeline - Implementation Targets: The revised Timeline identifies a 04/01/2020 date for “Contract start date”. Are there target dates or expectation about when the solution would go live in the marketplace (e.g. an Implementation Timeline)?

Pursuant to AB 466 Section 1(9), the System must begin operating by July 1, 2020.

3. Technical Requirements - 3rd Party Integration: Will state require platform to be agnostic and allow for 3rd party processors and financial entities who wish to participate within the NV closed loop platform?

The State will defer to each individual vendor’s system design.

4. Implementation - Project Leadership: Will the State have a single designated Implementation Lead or will the implementation responsibilities be spread across the leadership of the relevant State departments?

The State anticipates having a single designated individual act as a lead; however, the lead will coordinate implementation across all relevant divisions and agencies.

5. Scope of Work #2.5.5: Scope of Work #2.5.5 states: CLPPS servers, hardware, and any other physical or otherwise related components and any servers, hardware, and any other physical or otherwise related components controlled by a subcontractor must be physically located in Nevada. Is this physical location in Nevada a firm requirement or will you consider alternative locations?

This is a firm requirement.

6. Scope of Work #2.1.2: Scope of Work #2.1.2 states: All Vendor(s) systems, functions, products, devices, physical items, and any other components, must be created, established, offered, maintained, operated, and otherwise used in compliance with all federal, state, and local laws and regulations. Failure to do so will result in automatic termination of the contract for cause by the State. Please explain further as it is our understanding that possessing or selling Marijuana, and the processing of payments associated with sales is illegal under federal law.

Given the anticipated difference in each individual vendor’s system design, the State cannot provide guidance as to the legality of a system and its related functions.

ALL ELSE REMAINS THE SAME FOR RFP 05TO-S953.

Vendor must sign and return this amendment with proposal submitted.

Vendor Name:

Authorized Signature:

Title:

Date:

This document must be submitted in the “State Documents” section of vendors’ technical proposal.

Amendment # 2 RFP # 05TO-S953 Page 1 of 1 image1.wmf oleObject1.bin