Questions - answers.xls
XLS spreadsheet 41 KB Posted
- Attached to
- Online Crash Reports and Investigative Tools
- Solicitation number
- 65DPS-S2410
- Issued by
- Churchill County, Nevada
About this file
This document contains a Q&A related to a Request for Proposal (RFP) for an Online Crash Reports and Investigative Tools contract opportunity issued by the Nevada Highway Patrol (NHP). The RFP is seeking a vendor to provide an interface with NHP's Brazos crash data system to generate, redact, and sell crash reports to the public. Key details include a required online payment system, an annual volume of approximately 22,500 crash reports sold, and the ability to link the system to other law enforcement software. The anticipated project start and go-live date is November 1, 2023, but the overall budget is undetermined.
Regarding pricing, the state has a set $10 fee for crash reports that vendors are not allowed to exceed. There are no known state restrictions on data aggregation. References should be vendor-specific. Vendors are expected to provide technical details as part of their response to the Scope of Work, and the state will review all proposals to determine the best fit, without any stated technology preferences.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 65DPS-S2410 - Online Crash Reports and Investigative Tools - RFP - Final.docx | DOCX document | |
| Insurance Requirements - RFP.pdf | ||
| Terms and Conditions for Services 2023-04-13.pdf | ||
| Reference Questionnaire 2023-04-13.docx | DOCX document | |
| Standard Form Contract .pdf | ||
| Letter of Intent - CARFAX.docx | DOCX document | |
| Proposed Staff Resume 2023-04-13.docx | DOCX document | |
| Quote Instructions.pdf | ||
| 65DPS-S2410 Cost Schedule.doc | DOC document | |
| Attachments for Signatures 2023-04-13.pdf |
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 | MELISSAC@AFFINITY.COM | Mandatory Requirements | 1. Please confirm a NV business license is not required for RFP response/proposal submission, but rather it must be obtained prior to contract execution with the selected vendor. | Correct. | |
| 2 | MELISSAC@AFFINITY.COM | Crash Report Sales Volume | What volume of crash reports are provided to the public through the current manual process? | 22,500 +/- | |
| 3 | MELISSAC@AFFINITY.COM | Crash Report Fees | Does the State of Nevada have a set fee for the sale of a crash report? If so, is the price set in State statute? Is the vendor allowed to charge more than that price for their overhead/fees? | $10. Vendor not allowed to charge additional fees, not set by statute. | |
| 4 | MELISSAC@AFFINITY.COM | Purchaser Verification | When a person wishes to purchase a crash report, does the State have any requirements of vetting the purchaser? For example, must that person have an association with the crash (e.g., party in the crash, insurance company for the crash, etc.). | Purchaser needs to have Crash number, Last Name of Involved Party, and date of crash. | |
| 5 | MELISSAC@AFFINITY.COM | Querying Crash Reports | Is there an established set of criteria required for performing crash reports searches prior to purchase (e.g., Crash date & county, Crash date & name, etc.)? | Purchaser needs to have Crash number, Last Name of Involved Party, and date of crash. | |
| 6 | MELISSAC@AFFINITY.COM | Crash Report Generation | Is the purchased crash report to be formulated by the proposed system from crash report data elements, or is the report (e.g., pdf) provided as part of the Brazos data feed? If the proposed system is to generate a crash report, please provide samples of the State's crash report form. | ||
| Also, is there a preferred electronic format for the purchased report (e.g., pdf, HTML web page, emailed rich text report, etc.)? | Crash report is created from Brazos data feed. It is put in a PDF format with certain fields redacted. | ||||
| 7 | MELISSAC@AFFINITY.COM | Brazos Export Electronic Format | Is there an established electronic export format from Brazos? If so, please provide a sample. | Yes. (NHP does not see that part of it) | |
| 8 | MELISSAC@AFFINITY.COM | Brazos Data | Will the export from Brazos be a limited data set, or will it include PII data fields that need to be redacted at the time of the crash report purchase? If redaction is required, please provide a list of crash report data fields that cannot be released to the public. | It might include PII that needs to be redacted. |
PII:
All Juvenile info License Plate
| 9 | MELISSAC@AFFINITY.COM | File Types for Brazos Data | Will the crash data from Brazos include scanned documents or images (e.g., pdf, jpg)? | Yes, witness statements. PDF Files | |
| 10 | MELISSAC@AFFINITY.COM | Purchaser Information | What data does NHP expect to collect on each sold transaction? For example, the purchasers Name? email address? etc.? | Purchasers name, email address and amount paid | |
| 11 | MELISSAC@AFFINITY.COM | Vehicle License Plate Investigation | What investigative needs are there with respect to the requirement "regarding vehicle license plate information"? | vehicle history report & search by license plate | |
| 12 | MELISSAC@AFFINITY.COM | System Investigations | What types of investigations are done by this system? For example, is this a query to look up crash reports by crash data elements? Is heat mapping desired? If there are analytical needs, please define them. | vehicle history report & search by license plate | |
| 13 | MELISSAC@AFFINITY.COM | System Interfaces | Please provide examples of an ability to "link with other law enforcement software". | looks to be a duplicate question, must be able to interface with Brazos | |
| 14 | MELISSAC@AFFINITY.COM | Crash Doc Customers | What are "Crash doc customers" and what is their anticipated use of the new system? | Crash doc customers meaning involved party, insurance company or legal representative | |
| 15 | MELISSAC@AFFINITY.COM | Data Governance | Are there any State restrictions on data aggregation that would relate to this purchase? For example: hosting Nevada crash data on systems containing another entity's crash data, performing multi-entity analytics using Nevada data in combination with other client data, trending purchases of crash data between clients, etc. | no known state restrictions with regard to data aggregation | |
| 16 | TYLERTECH2 | Crash report fee structure | Is there a different pay structure for different types of crash reports? | No | |
| 17 | TYLERTECH2 | # of Crash Reports sold | How many crash reports are sold annually? | 22500 +/- | |
| 18 | TYLERTECH2 | Crash Doc | Does NHP intend to keep the Crash Doc product (as referenced in item 3.2.2 of the RFP)? | Unsure at this time | |
| 19 | CMARCHETTI | Interface with Brazos | 1. | In section 2.2.7, you call for an ?interface? with your vendor (Brazos). How do you define ?interface.?? What written requirements do you have? Please expand on the desired architecture. Currently, the data exchange is accomplished with data export. | An automatic interface sends crashes from Brazos once they are approved to Crash Report vendor. |
| 20 | CMARCHETTI | uploading of reports | 2. | What requirements do you have for a workaround or manual process if the automatic uploading of reports is not working? | Front office staff redact doc from Brazos and send |
| 21 | CMARCHETTI | Redactions | 3. | What redactions would be needed other than what is currently being redacted? | None at this time |
| 22 | CMARCHETTI | "link" to software | 4. | What software would NHP like us to ?link? to? What goal would this accomplish? What are the requirements for this ?link?? | Unsure what this refers to |
| 23 | CMARCHETTI | "link" to software | 4. | What software would NHP like us to ?link? to? What goal would this accomplish? What are the requirements for this ?link?? | Unsure what this refers to |
| 24 | CMARCHETTI | "link" to software | 4. | What software would NHP like us to ?link? to? What goal would this accomplish? What are the requirements for this ?link?? | Unsure what this refers to |
| 25 | CMARCHETTI | Q&A | Will all questions posted and answers be able to be viewed by all vendors regardless of who asked the question? | Yes. | |
| 26 | INFO@MS2SOFT.COM | Online payment requirement | We are a leading provider of Traffic Crash Data and Online Crash Reports in North America. Our commercial-off-the-shelf (COTS) system is used by around 30 entities in 11 States. Would a solution that meets all other requirements, but doesn't offer an online payment option be considered as this model is not common in this market? | No | |
| 27 | INFO@MS2SOFT.COM | Online payment purpose | Is the purpose of online payment to limit who the information is available to, to offset the cost of the system, or other reasons? | the purpose is "one stop shop", no human interaction needed | |
| 28 | IXRFP | COTS | Do you expect this to be a product offering or a custom solution that is specifically built for you? |
| Do you have any technology preferences? | whichever is the best fit, preferences unknown at this time | |||
| 29 | IXRFP | Tool | Apart from Brazos are there any other 3rd party systems that need to be integrated with the system? |
Do you expect the system to have any BI/Reporting capabilities?
| Should the proposal include the technical solution too as part of the "Response to Scope of Work"? | Other 3rd party systems unknown at this time. There is an expectation of accounting reports and number of reports purchased within customized time frames. | |||
| 30 | IXRFP | General | What is the anticipated project start and go-live date? |
What is the overall budget associated with this project?
| Can we propose a hybrid resource (Onshore-Offshore) model to accomplish the project? | the anticipated go live date is Nov 1, 2023, the budget is undetermined and we will review all proposals. | ||||
| 31 | IXRFP | Reference | Can the reference be vendor-specific or should it be a proposed staff-specific reference? | Vendor specific. |
File details come from the government source that posted it. Updated .