Editable Attachments A - D.xlsx
XLSX spreadsheet 29 KB Posted
- Attached to
- Dairy Inspection and Licensing Software System
- Solicitation number
- 55AGR-S2926
- Issued by
- Washoe County, Nevada
About this file
The provided document is a government file related to a state and local contract opportunity for a cloud-based dairy inspection and licensing software system, issued by the Nevada Department of Agriculture (NDA) for Washoe County, Nevada. The system must manage the state's dairy inspection program, including permits, licenses, inspections, data collection, and reporting, while complying with federal and state dairy regulations. Key requirements include offline capabilities, review and approval workflows, integration with existing systems, and compliance with state and federal security standards. The NDA has issued a Request for Information (RFI) to gather cost estimates and proposed solutions from vendors, with a deadline for questions on August 30, 2024, and a submission deadline of September 20, 2024. The information gathered through the RFI responses will be used for budget justification or to develop a subsequent solicitation, but no contract award will result from this RFI.
The RFI does not specify a budget range or possible award value, as the information gathered will be used for future planning and potential solicitation development. It also does not mention any incumbent vendors or current contractors, nor does it provide details on existing infrastructure or technology that requires integration. The contract opportunity is specific to Washoe County, Nevada, and no set-aside designations or restrictions on the types of organizations that can respond are mentioned in the provided information.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI-Dairy inspection and Licensing.pdf | ||
| Quote Instructions.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
Attachment A
| Attachment A - Permits and Inspections Functional Requirements | ||||
| CATEGORY | FUNCTIONAL REQUIREMENTS | Available | Not Available | Comments |
| All requirements listed as required in the field must be available when offline. | ||||
| Inspections | The system should provide the ability to conduct environmental health inspections. | |||
| Inspections | The system must have a mechanism for an authorized user or supervisor to review, comment, and modify inspection reports. | |||
| Inspections and Scheduling | The system must allow users to schedule inspections for dairy farms, plants, and single service container manufacturers. | |||
| Inspections and Scheduling | The system must support recurring/re-inspection schedules based on regulatory requirements. | |||
| Inspections and Scheduling | The system can alert authorized staff to what inspections / sample collections are due and assist with scheduling and placing on calendar. | |||
| Data Collection and Entry | The system must provide digital forms for data entry during inspections. | |||
| Data Collection and Entry | The system must allow users to enter data offline and synchronize when online. | |||
| Data Collection and Entry | Users must be able to attach photos, videos, and other files to inspection records. | |||
| Data Collection and Entry | The system must provide the ability to upload satellite images of a facility and maps so inspector can easily navigate to and around the facility. | |||
| Data Collection and Entry | The system must provide the ability to store contact information on all facilities and allow inspection staff to access the contact information while in the field. | |||
| Violation Logging | The system must allow users to log violations observed during inspections. | |||
| Violation Logging | The system must support documenting corrective actions and tracking their status. | |||
| Form Generation and Management | The system must automatically populate required reulatory forms based on the inspection type. | |||
| Form Generation and Management | Users must be able to review, edit, and approve forms before submission. All forms will be digitally archived. | |||
| Communication and Notifications | The system must allow users to send notifications and emails to dairy operators regarding inspection results and approvals, corrective action updates, and upcoming deadlines. | |||
| Reports | The system must be able to calculate a numerical score onto the inspection report. Each violation has a point value that corresponds to it. It's a calculated score based on inspection results. | |||
| Plan Review | The system should provide a mechanism to perform plan review approval and allow the customer to see the approval status. | |||
| Fiscal Management for Permits | The system must be able to generate various dairy permits. | |||
| Fiscal Management for Permits | The system must provide a mechanism for authorized and external users to schedule testing to obtain a permit / revoke permit. | |||
| Client Portal for Inspections and Permits | The system must provide a client login to see inspection scores, inspection reports, permits, approval status, warning letters, and lab results. |
Attachment B
| Attachment B - Licensing Funtional Requirements | ||||
| CATEGORY | FUNCTIONAL REQUIREMENTS | Available | Not Available | Comments |
| All requirements listed as required in the field must be available when offline. | ||||
| Licensing | The system must provide a mechanism for dairy retailers, distributors, and processing plants to enter their annual license application and make payments. | |||
| Licensing | The system must provide a mechanism for dairy retailers, distributors, and processing plants to keep track of licensees that are exempt from filing remittances. | |||
| Fiscal Management for Licensing | The system must provide a mechanism for collecting and tracking financial data for distributor licenses and monthly remittances. | |||
| Data Collection and Entry | The system must provide a mechanism for licesnsee to fill in their monthly remittance forms and make payments. It is required for the system to interface with the State's preferred payment gateway. | |||
| Client Portal for Licensing | The system must provide a client login to report sales and be able to calculate tax on reported sales to make remittances. |
Attachment C
| Attachment C - Shared Functional Requirements | ||||
| CATEGORY | FUNCTIONAL REQUIREMENTS | Available | Not Available | Comments |
| All requirements listed as required in the field must be available when offline. | ||||
| User Management | The system must be able to create, edit, delete, suspend, and disable users. | |||
| User Management | The system must be able to change passwords, perform password resets, force password changes, and lock out users. | |||
| User Management | The system must support different user roles like inspectors, administrators, and dairy operators with role-based access control. | |||
| Data Collection and Entry | The system must allow users to enter data offline and synchronize when online. | |||
| Communication and Notifications | The system must allow users to send both scheduled and ad-hoc notifications and emails to dairy operators and distributors regarding inspection results, approvals, corrective action updates, and upcoming deadlines. | |||
| Reports | The vendor must describe standard reporting suite and the process for creating custom reports. | |||
| Data Migration | The system must provide the ability to migrate 2 years of legacy data into the new system. | |||
| Payment/Invoicing | Clients shall be able to pay by cash or check for licensing, remittance, permits, and/or fines through the system. | |||
| Auditing and Security | The system must provide a mechanism for authorized auditors to audit the financial information and adjust or write off as needed. | |||
| Auditing and Security | Users must have access only to the data and functionalities relevant to their roles. | |||
| Integration | The system must provide APIs for integration with external systems, such as the State financial system, payment portals, and the LIMS system. | |||
| User Interface | The system must comply with accessibility standards to accommodate users with disabilities. | |||
| Backup and Recovery | The system must perform regular data backups to prevent data loss and restore data in case of system failures. | |||
| Documentation and Training | The vendor must provide documentation and training to all authorized users / NDA staff. |
Attachment D
| Attachment D - System Security Requirements | |||
| System Security Requirements | Available | Not Available | Comments |
| All requirements listed as required in the field must be available when offline. | |||
| FEDERAL SECURITY REQUIREMENTS | |||
| The system must comply with the National Institute of Standards and Technology (NIST) SP 800-53 for storing, processing, and transmitting federal data. https://csrc.nist.gov/publications/detail/sp/800-53/rev-4/final | |||
| STATE SECURITY REQUIREMENTS | |||
| Cloud Service Providers (CSPs) offering Infrastructure as a Service (IaaS) must be able to demonstrate or show proof of comparable controls and processes needed to meet FedRAMP certified requirements or Center for Internet Security (CIS) controls identified as applicable to IaaS service models in the current CIS Controls Cloud Companion Guide. https://www.cisecurity.org/controls/ | |||
| CSPs offering Platform as a Service (PaaS) must be able to demonstrate or show proof of comparable controls and processes needed to meet FedRAMP certified requirements or CIS controls identified as applicable to PaaS service models in the current CIS Controls Cloud Companion Guide. https://www.cisecurity.org/controls/ | |||
| CSPs offering Software as a Service (SaaS) or any other cloud service model not explicitly named in this standard must be able to demonstrate or show proof of comparable controls and processes needed to meet the current version of CIS controls identified as applicable to SaaS service models in the current CIS Controls Cloud Companion Guide or SOC 2 Type 2. https://www.cisecurity.org/controls/ | |||
| CSPs offering Function as a Service (FaaS) must be able to demonstrate or show proof of comparable controls and processes needed to meet the current version of CIS controls identified as applicable to FaaS service models in the current CIS Controls Cloud Companion Guide or SOC 2 Type 2. https://www.cisecurity.org/controls/ | |||
| CSP data centers, staff, and contractors collecting, processing, transmitting, storing, or interconnecting State data in a cloud environment must be located within the continental United States. | |||
| The system must require Multi-Factor Authientication (MFA) when any user is connecting to or accessing the system. | |||
| Cloud services must enforce least-privilege access to data, based on access roles established or agreed to by the agency. | |||
| The vendor must meet or exceed the State of Nevada Information Security Policies, Standards, and Procedures. https://it.nv.gov/Governance/Security/State_Security_Policies_Standards___Procedures | |||
| The system must be compliant with Nevada Revised Statutues NRS 242 Information Services. https://www.leg.state.nv.us/NRS/NRS-242.html | |||
| The system must meet State security standards for encryption of personal information for data at rest, in transit, and when data is active. NRS 205.4742 Encryption https://www.leg.state.nv.us/Division/Legal/LawLibrary/NRS/NRS-205.html#NRS205Sec4742 and NRS 603A. Security and Privacy of Personal Information https://www.leg.state.nv.us/Division/Legal/LawLibrary/NRS/NRS-603A.html | |||
| The vendor must preserve, discard, or destroy any application systems and information that become obsolete and are no longer used in accordance with Electronic Record and Record Management requirements defined in NRS 239 and NAC 239 - Public Records, for Records Management. https://www.leg.state.nv.us/Division/Legal/LawLibrary/NRS/NRS-239.html https://www.leg.state.nv.us/Division/Legal/LawLibrary/NAC/NAC-239.html | |||
| The system must utilize the existing State Multi-Protocol Label Switching (MPLS) connection for the transmission of data. Optimizing the MPLS connection will ensure minimal impact for all services using this same connection. | |||
| AGENCY SECURITY REQUIREMENTS | |||
| The system must have documented security specifications that include an analysis of security risks and recommended controls, including access control systems and contingency plans. | |||
| The vendor must provide a Test environment separate from the Production and Development environments which will be included with cloud hosting and have documented Deployment Procedures. | |||
| The vendor must be able to perform quarterly vulnerability scans on its network and applications and report to the NDA within 10 business days from the end of each quarter showing confirmation that the scan was completed and that any vulnerabilities found have been resolved, or the expected date of resolution. | |||
| The vendor must provide the NDA, at no additional cost, two data extractions, one within thirty (30) days of contract termination notification, and a final extraction of data upon termination of the contract. The extractions will be a complete backup copy of the production database in a format acceptable to the State and delivered via a method acceptable to the State. | |||
| System hosting may be with the Nevada Officer of the Chief Information Officer (OCIO) Computing Services and must comply with OCIO standards. https://it.nv.gov/Governance/Security/State_Security_Policies_Standards___Procedures/ | |||
| The system must be able to authenticate all users accessing the system. |
File details come from the government source that posted it. Updated .