Attachment 4 Information Technology Requirements.xlsx
XLSX spreadsheet 15 KB Posted
- Attached to
- Elections Campaign Finance Software
- Solicitation number
- RFP-2500004795
- Issued by
- Arizona
About this file
This document is an Attachment 4 Information Technology Requirements spreadsheet for Pima County, Arizona, specifically related to an Elections Campaign Finance Software procurement. The detailed matrix outlines comprehensive IT requirements across multiple domains including security, encryption, access management, data handling, and service level agreements (SLAs). The requirements are structured to evaluate software solutions across both cloud and on-premises deployment models, with specific emphasis on features like multi-factor authentication, role-based access permissions, single sign-on compatibility, and robust security protocols.
The requirements document demonstrates Pima County's rigorous technical evaluation criteria, with specific expectations for software performance, including 99% service uptime, rapid response times for critical and high-priority issues, and comprehensive security measures such as data encryption in transit and at rest, audit logging capabilities, and password management protocols. Notable technical specifications include potential integration with ESRI/ArcGIS platforms, support for custom URLs, FEDRAMP compliance, and the ability to provide technical documentation. The county also emphasizes data ownership, with a clear stipulation that Pima County retains ownership of all collected data, and requires vendors to provide full disclosure of user data collection practices.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP-2500004795 Election Campaign Finance Software.pdf | ||
| Attachment 3 Software Requirements.xlsx | XLSX spreadsheet |
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
IT Requirements
| INFORMATION TECHNOLOGY REQUIREMENTS | Yes - Software/System meets both minimum and recommended requirements | ||||||||
| Name of the proposed Software / System: | Yes - Software/System meets minimum requirement but not recommended requirement | ||||||||
| Link to the Software / System Website: | Yes - Software/System meets minimum requirement (no recommended requirement presented) | ||||||||
| Reference | Category | Requirement | Software Type | Minimum Requirement | Recommended Requirement | Software Meets Requirements | Notes | ||
| (If requirement is N/A, please explain) | Yes - Software/System meets recommended requirement (no minimum requirement presented) | ||||||||
| Cloud | On Prem | Both | Yes | No | N/A | No - Software/System cannot meet any presented requirement | |||||||
| I.1 | General | ESRI/ArcGIS if applicable | Both | ArcGIS Pro 3.x | |||||
| ArcGIS Enterprise 11.x | N/A - Presented requirements do not apply to this Software/System | ||||||||
| I.2 | Security | Vendor pushes/provides security patches or vulnerability remediation | Both | As needed | |||||
| I.3 | Security | Does not require anti-virus exceptions | Both | If exception detailed list must be provided | No exceptions | ||||
| I.4 | Security | Solution utilizes a Web Application Firewall or provides option to utilize Pima County's (Cloudflare) | Cloud | ü | |||||
| I.5 | Security | Installation/application files are digitally certified | Both | Hash is available | Digitally signed by trusted 3rd party | ||||
| I.6 | Encryption | Data is encrypted in transit and at rest | Both | ü | |||||
| I.7 | Encryption | Passwords are encrypted | Both | ü | |||||
| I.8 | Audit | Application performs audit logging. | Both | ü | |||||
| I.9 | Audit | Ability to list users by their access group/access role | Both | ü | |||||
| I.10 | Updates | Provides ongoing application support and maintenance including patches for known vulnerabilities, troubleshooting failed updates. | Both | ü | |||||
| I.11 | Updates | Provides a schedule of patch/feature releases, details, downtime advisement, installation instructions, day-one impact prior to release | Both | Patches = as soon as ready |
Features = 1 month advance notice
| I.12 | Updates | Provides sandbox or test environment prior to feature release | Cloud | ü | |
| I.13 | Updates | Can opt-out of specific feature enhancements | Cloud | ü | |
| I.14 | Access | Local admin privileges are not needed for application maintenance, support, or installation. | Both | ü | |
| I.15 | Access | Solution supports use of custom URLs (custom domain & certs) | Cloud | ü | |
| I.16 | Access | Passwords can be changed as needed | Both | ü | |
| I.17 | Access | Supports Microsoft Single Sign On | Both | ü | |
| I.18 | Access | Role based access permissions are supported | Both | ü | |
| I.19 | Access | Supports Microsoft Multi-factor Authentication | Both | ü | |
| I.20 | Access | Account lockout functionality exists | Both | ü | |
| I.21 | Access | Has minimum password length and complexity requirements | Both | ü | |
| I.22 | Access | Has password expiration functionality | Both | ü | |
| I.23 | Access | Has configurable auto logout (such as time-out functionality) | Both | ü | |
| I.24 | Access | Software offers a work offline and synch option if applicable | Both | ü | |
| I.25 | Access | FEDRAMP compliant | Both | ü | |
| I.26 | Data | Vendor provides full disclosure of any user data collected | Cloud | ü | |
| I.27 | Data | Pima County retains ownership of all data | Cloud | ü | |
| I.28 | Data | Technical documentation should be readily available | Both | ü | |
| I.29 | Data | The solution can integrate with industry standard mapping/GIS/geographic software if applicable | Both | ü | |
| I.30 | SLA | Software service uptime is 99% outside of scheduled maintenance. | Cloud | ü | |
| I.31 | SLA | Service response time for critical issues is one-hour. |
Service response time for high issues is four-hours.
| Service response for all other issues is same day. | Both | ü | |
| I.32 | SLA | Service resolution time for critical issues is four hours. |
Service resolution time for high issues is within 2 business days.
| Resolution for all other issues is within five business days. | Both | ü | ||||
| I.33 | SLA | Maintains and executes a multi-channel outage communication plan to include a status page and email notification of planned outages, and real-time notification of non-planned outage/degradation events and estimated resolution time. | Cloud | ü | ||
| I.34 | System Requirements | Has an API library to integrate effectively with other systems if required | Both | ü |
&"Georgia Pro Cond Light,Bold"&18A&14TTACHMENT &16 4&14: &18I&14NFORMATION &18T&14ECHNOLOGY &18R&14EQUIREMENTS
File details come from the government source that posted it. Updated .