Questions - Answers.xls
XLS spreadsheet 28 KB Posted
- Solicitation number
- 65DPS-S2959
- Issued by
- Nevada
About this file
This document contains a set of questions and answers related to a bid for an "All in One Officer Accountability Reporting and Tracking Program" issued by the State of Nevada Department of Public Safety (NVDPS). The RFP seeks proposals for a customizable, electronic system that can import and convert existing data to provide features such as training tracking, use of force and pursuit monitoring, crash reporting, racial bias tracking, and early warning alerts. The contract term is expected to be four years, subject to Board of Examiners approval, with a targeted award date in December 2024 and a start date in January 2025. Vendors must provide financial information, business references, and proposed staff resumes as part of their proposal submissions.
The pricing proposals will be evaluated based on a formula considering the lowest cost submitted, and the State reserves the right to require vendor presentations as part of the evaluation process. The procurement does not appear to include any set-aside designations or restrictions on the types of organizations that can respond. The RFP does not mention any incumbent vendors or current contractors, nor does it provide information on any existing infrastructure or technology that requires integration. While the RFP states the expected contract term and a targeted award date, it does not specify a budget range or maximum award value.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachments for Signatures 2023-04-13~6.pdf | ||
| 65DPS-S2959 Cost Schedule.xlsx | XLSX spreadsheet | |
| Proposed Staff Resume 2023-04-13~5.docx | DOCX document | |
| Reference Questionnaire 2023-04-13~5.docx | DOCX document | |
| Standard Form Contract ~5.pdf | ||
| 65DPS-S2959 RFP All in One Officer Account.docx | DOCX document | |
| Terms and Conditions for Services 2023-04-13~5.pdf | ||
| Questions - Answers round 2.xls | XLS spreadsheet | |
| 65DPS-S2959 RFP All in One Officer Account - Updated.pdf | ||
| 65DPS-S2959 - Insurance Schedule - RFP.pdf | ||
| Quote Instructions.pdf |
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Bid Q&A for Export Report
| Bid Q&A | ||||
| QUESTION_NBR | CREATED_BY | QUESTION_SUBJECT | QUESTION_TEXT | ANSWER_TEXT |
| 1 | SALESOPS | User count | Please provide the total user count requiring access to the system. | 1,700 |
| 2 | SALESOPS | Mandatory Minimum Requirements (7.4 & 7.5) | Some of the mandatory minimum requirements aren't aligned with the offerings that Axon typically offers to customers. Based on the scope of this RFP, is there any possibility of movement on re-defining the language in the mandatory minimum requirements to ensure that it is better aligned with what we are able to offer? | Mandatory minimum requirements must be addressed. Redlines will be reviewed and accepted if allowable. |
| 3 | WFLAVIN@SALESFORCE.COM | SaaS | Would DPS consider a low code/no code platform like Salesforce for this solution? | We would consider if everything outlined in the scope of work and deliverables are met. |
| 4 | WFLAVIN@SALESFORCE.COM | Demos | What softwares/solutions has DPS seen demos of leading up to this RFP being released? | None |
| 5 | WFLAVIN@SALESFORCE.COM | SaaS | Does DPS have a platform or technology preference for this project? | Presently DPS’s IT Dept does not have the ability to provide Azure Support within the agency. This does not mean that we can't have Azure solutions, it means that the vendor needs to know that we cannot standup those Azure resources in our tenant. And we cannot directly support Azure resources in a different tenant. If a SaaS solution is presented the SaaS resources must be created and supported entirely by the vendor. Our IT Dept can assist with tenant identity connections and things like that (Single Signon and whatnot). They just can't support full stack development. |
File details come from the government source that posted it. Updated .