2-Attachment B - Functional and Technical Requirements.xlsx
XLSX spreadsheet 17 KB Posted
- Attached to
- Agenda Management Software Solution
- Solicitation number
- 260201
- Issued by
- Sedgwick County, Kansas
About this file
This is a Functional and Technical Requirements matrix for an Agenda Management Software Solution being procured by the City of Wichita, Kansas for the City Clerk's office. The document outlines a comprehensive set of required and desired capabilities organized across four primary categories: Technical, Security (Access), Reports, and Integration. All requirements listed are marked as "Required" baseline functionality with no items designated as desired, third-party applications, planned for future release, or requiring source code modifications.
The technical requirements include reporting on separate databases, batch processing capabilities, application server separation from database servers, API and web service interfaces for external system integration, PCI compliance, dual monitor support, client-interface-based job management, and critical stipulations that AI systems cannot use City data for model training or retraining while ensuring all City data remains owned and controlled by the City. Security requirements mandate compliance with relevant standards such as ISO 27001, SOC 2, GDPR, and HIPAA; role-based access control; multi-factor authentication support; AES-256 encryption for data at rest and TLS 1.2+ for data in transit; comprehensive audit logging; secure credential storage; and regular penetration testing. Reporting requirements call for built-in or integrable reporting engines compatible with platforms such as Power BI or Tableau, ad-hoc and scheduled report generation, multiple export formats (PDF, Excel, CSV), role-based report access, KPI dashboards, audit trails for report activities, and customizable filtering and grouping. Integration requirements specify compatibility with existing systems including ERP, SSO, and payment gateways, as well as support for both file-based and API-based data exchange methods.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 1-RFP 260201 Solicitation Document.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
Functional and Tech Req Appendix B Functional and Technical Requirements Criteria Matrix
| ID | Requirement Task | Required | Desired | Baseline | Third Party App. Req. | Planned for Future Release | Req. Source code Mods. | Not Available | Vendor Comments |
| 1.00 | TECHNICAL | ||||||||
| 1.01 | Reporting on separate Databases | X | |||||||
| 1.02 | Batch Processing | X | |||||||
| 1.03 | Application Server separate from Database server | X | |||||||
| 1.04 | API / Web Service Interfaces between External Systems | X | |||||||
| 1.05 | PCI Compliance | ||||||||
| 1.06 | Ability to view different screens on dual monitors | X | |||||||
| 1.07 | Jobs are managed through the client interface (no direct access to the servers) | X | |||||||
| 1.08 | AI systems do not use City Data for model training, retraining, fine-tuning, or model improvement. | X | |||||||
| 1.09 | All City Data entered into, processed by, or stored within the application remains owned and controlled by the City. | X | |||||||
| Totals | 0 | 0 | 0 | 0 | 0 | ||||
| 2.00 | SECURITY (Access) | ||||||||
| 2.01 | Compliance with relevant security standards (e.g., ISO 27001, SOC 2, GDPR, HIPAA). | X | |||||||
| 2.02 | Role-based access control (RBAC) and user permission management. | X | |||||||
| 2.03 | Authentication protocols (OAuth2, SAML, LDAP, MFA support). | X | |||||||
| 2.04 | Data encryption (AES-256 for data at rest; TLS 1.2+ for data in transit). | X | |||||||
| 2.05 | Audit logging of all user and system activities. | X | |||||||
| 2.06 | Secure storage of credentials and secrets (e.g., using Vault or KMS). | X | |||||||
| 2.07 | Regular penetration testing and vulnerability scans. | X | |||||||
| Totals | 0 | 0 | 0 | 0 | 0 | ||||
| 3.00 | REPORTS | ||||||||
| 3.01 | Built-in or integrable reporting engine (e.g., Power BI, Tableau, custom). | X | |||||||
| 3.02 | Ad-hoc and scheduled report generation. | X | |||||||
| 3.03 | Export formats: PDF, Excel, CSV. | X | |||||||
| 3.04 | Role-based access to reports. | X | |||||||
| 3.05 | Dashboards for KPIs and operational metrics. | X | |||||||
| 3.06 | Audit trails for report views/downloads. | X | |||||||
| 3.07 | Customizable filters and grouping. | X | |||||||
| Totals | 0 | 0 | 0 | 0 | 0 | ||||
| 4.00 | Integration | ||||||||
| 4.01 | Integration with existing systems (e.g., ERP, SSO, payment gateways) | X | |||||||
| 4.02 | Support for file-based (CSV, XML) and API-based data exchange. | X | |||||||
| Totals | 0 | 0 | 0 | 0 | 0 | ||||
| Baseline | Third Party App. Req. | Planned for Future Release | Req. Source code Mods. | Not Available | |||||
| Grand Totals | 0 | 0 | 0 | 0 | 0 |
Page &P of &N
File details come from the government source that posted it. Updated .