2-Attachment B - Functional and Technical Requirements.xlsx
XLSX spreadsheet 16 KB Posted
- Solicitation number
- 250350
- Issued by
- Sedgwick County, Kansas
About this file
This is a Functional and Technical Requirements document for a software application system for the City of Wichita Transit Department's Digital Signage project for the new Multimodal Transit Facility (The HUB). The document presents a criteria matrix outlining required, desired, baseline, third-party application, and future-release specifications across four primary categories: Technical requirements, Security (Access) requirements, Reports functionality, and Integration capabilities. The technical requirements encompass eight items including software performance efficiency, database reporting capabilities, batch processing, application server separation, API/web service interfaces, PCI compliance, dual monitor display functionality, and job management through client interfaces. No specific response dates, due dates, site visits, bidder meetings, award dates, or contract terms are identified within this requirements document.
The Security (Access) section specifies seven requirements focused on compliance with industry standards (ISO 27001, SOC 2, GDPR, HIPAA), role-based access control, authentication protocols (OAuth2, SAML, LDAP, MFA support), data encryption standards (AES-256 at rest; TLS 1.2+ in transit), audit logging, secure credential storage, and penetration testing. The Reports section includes seven requirements for reporting engine functionality, ad-hoc and scheduled report generation, export capabilities (PDF, Excel, CSV), role-based report access, KPI dashboards, audit trails, and customizable filters. The Integration section specifies two requirements for compatibility with existing systems (ERP, SSO, payment gateways) and support for file-based and API-based data exchange. All items are marked as required with no items categorized as desired, baseline, third-party application requirements, or planned for future release, indicating comprehensive mandatory functionality expectations.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 4-Attachment D - FTA Clauses and Forms.pdf | ||
| 3-Attachment C - Drawings.pdf | ||
| 1-RFP 250350 Solicitation Documents.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 | Efficiency in software performance | X | |||||||
| 1.02 | Reporting on separate Databases | X | |||||||
| 1.03 | Batch Processing | X | |||||||
| 1.04 | Application Server separate from Database server | X | |||||||
| 1.05 | API / Web Service Interfaces between External Systems | X | |||||||
| 1.06 | PCI Compliance | X | |||||||
| 1.07 | Ability to view different screens on dual monitors | X | |||||||
| 1.08 | Jobs are managed through the client interface (no direct access to the servers) | 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 .