2-Attachment B Functional and Technical Requirements Matrix.xlsx
XLSX spreadsheet 27 KB Posted
- Solicitation number
- 260275
- Issued by
- Sedgwick County, Kansas
About this file
This document is a Functional and Technical Requirements Matrix for the City of Wichita, Kansas RFP #260275 for Location Intelligence and Visitation Analytics Services. The City of Wichita seeks to procure a vendor-hosted solution to support multiple City departments in analyzing visitor patterns, foot traffic, and demographic data across municipal properties and facilities. The requirements matrix outlines three primary categories of functionality: General System Requirements (16 items covering core visitation analysis, demographic insights, data visualization, and privacy protections), Desired Functional Specifications (10 items including retail leakage analysis, economic impact assessment, and automated reporting), and Value Added Services and Options (11 items encompassing implementation, training, custom analysis, and technical support). The solution must support authorized users from multiple City departments, allow creation of custom geographic boundaries and Points of Interest, and provide historical trend analysis with specified data update frequencies.
The document establishes mandatory technical requirements that vendors must satisfy, including vendor-hosted deployment accessible through standard web browsers, custom geographic area support, data export capabilities in common file formats, and compliance with the City's cybersecurity framework requirements (SOC 2 Type II or ISO/IEC 27001 certification). The solution must provide encryption of data at rest and in transit, user authentication and access controls, and maintain strict privacy protections by providing only aggregated and de-identified data without personally identifiable information or individual device identification capabilities. Vendors must disclose all material third-party data providers and subprocessors and provide documentation validating claimed security certifications. The requirements matrix uses a standardized evaluation methodology allowing proposers to indicate whether each requirement is met through standard functionality, configuration, custom development, third-party integration, planned future release, or is not available.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 1-RFP 260275 Solicittion 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
Table 1
| City of Wichita, KS: RFP #260275-Location Intelligence and Visitation Analytics Servcies | ||
| Attachment B - Functional and Technical Requirements Matrix | ||
| Locatin Intelligence and Visitation Analytics Services | Comments |
| "Standard Functionality" -Should be selected IF: Requirements are met out of the box. No configuration / customization to the product is needed. |
| "Configurable" -Requirements can be met with configuration. No customization needed. Example: Field names can change and values in drop down boxes added / deleted. |
| "Custom Development" - Requirement met through custom development (modification or additions to base code). |
| "3rd Party" - Requirements cannot be met within the system and will require another vendor's application / system to meet the requirements. |
| "Planned for Future Release" - This functionality will be part of a planned update to the product. If this is indicated, then the Proposer must place the version and anticipated release date in the comments section. |
| "Not Available" - This functionality is not supported and there is not a definitive plan to include in the next release. |
| ITEM | ||||||||
| INDEX | SF | C | CD | 3rd | PFR | NA | Comments | |
| 1 | General System Requirements | |||||||
| 1.1 | Visitation and Foot Traffic Analysis: Estimate visits and unique visitors to defined properties, facilities, and geographic areas. | |||||||
| 1.2 | Historical Visitation Analysis: Analyze visitation trends over time and generate new analyses for historical periods. Identify the earliest available data date and any limitations on retrospective analysis. | |||||||
| 1.3 | Time-of-Day and Day-of-Week Analysis: Analyze visitation patterns by hour, day of the week, and other available time intervals. | |||||||
| 1.4 | Dwell Time and Visitation Frequency: | Estimate how long visitors remain at a location and how frequently they return. | ||||||
| 1.5 | Visitor Origins and Trade Areas: Analyze aggregated visitor origins by ZIP code, census geography, distance traveled, or other available geographic measures. | |||||||
| 1.6 | Visitor Demographics: | Provide available aggregated demographic and market characteristics associated with visitors. | ||||||
| 1.7 | Visitor Journey Analysis: Analyze aggregated visitor activity before and after visiting a selected location. | |||||||
| 1.8 | Custom Points of Interest: | Allow City users to create, edit, and analyze custom geographic boundaries for parks, facilities, amenities, events, and other locations. | ||||||
| 1.9 | Comparative Location Analysis and Visitation Trends: Compare visitation and visitor characteristics among multiple City properties or other selected locations across selected dates, periods, and year-over-year intervals. . | |||||||
| 1.10 | Event Visitation Analysis: | Estimate attendance and visitation patterns for events occurring within defined geographic areas and time periods. | ||||||
| 1.11 | Data Visualization and Mapping: | Provide interactive maps, charts, graphs, and other visualizations of analytical findings. | ||||||
| 1.12 | Reporting and Data Export: Generate and export reports, tables, charts, and analytical results in commonly used formats. | |||||||
| 1.13 | Data Coverage and Update Frequency: | Identify geographic coverage, available historical periods, frequency of data updates, and known limitations. | ||||||
| 1.14 | Multiple Users and Service Areas: Support authorized users from multiple City departments or divisions within the proposed licensing arrangement. | |||||||
| 1.15 | Aggregated and De-identified Location Data / Privacy Protection: The solution shall not provide City users with personally identifiable information or individual-level device information. | |||||||
| 1.16 | Data Quality and Statistical Methodology Transparency: Provide documentation explaining the methodology used to generate visitation estimates, including data sources, sampling and extrapolation methods, data validation procedures, known limitations, and measures of statistical reliability or accuracy, where available. |
| 2 | Desired Functional Specifications |
| 2.1 | Retail Leakage and Demand Gap Analysis: Identify potential gaps between consumer demand and available retail or commercial services. |
| 2.2 | Business and Site Selection Analysis: Support evaluation of potential locations for businesses, facilities, and public investments. |
| 2.3 | Economic Impact Analysis: Estimate economic activity associated with facilities, events, tourism, or other destinations. |
| 2.4 | Workforce and Employee Analysis: Provide aggregated insights into workforce characteristics, commuting patterns, or employment-related activity. |
| 2.5 | Migration and Population Movement: Analyze population movement and changes in geographic activity patterns over time. |
| 2.6 | Marketing and Campaign Effectiveness: Evaluate changes in visitation associated with marketing initiatives, promotions, or outreach efforts. |
| 2.7 | Public Investment Before-and-After Analysis: Compare visitation and other available metrics before and after facility improvements, capital projects, or programming changes. |
| 2.8 | Automated and Scheduled Reporting: Generate or distribute recurring reports at user-defined intervals. |
| 2.9 | Public-Facing Data Visualization: Provide dashboards or visualizations suitable for sharing selected findings with external stakeholders or the public. |
| 2.10 | API and Automated Data Feeds: Support automated retrieval or integration of analytical data with other City systems. |
| 2.11 | GIS Compatibility: Support the use of geographic boundaries, spatial data, or exports compatible with the City's GIS environment. |
| 3 | Value Added Service and Options |
| 3.1 | Implementation and Onboarding: Provide initial setup, configuration, user account creation, and assistance establishing City properties and POIs. |
| 3.2 | Initial and Ongoing Training: Provide training for new and existing users, including tutorials, webinars, documentation, and other available resources. |
| 3.3 | Customer Success and Analytical Support: Provide ongoing assistance with platform functionality, report development, and analytical questions. |
| 3.4 | Data Validation and Methodology Support: Provide technical explanations, methodology documentation, and assistance interpreting visitation estimates and limitations. |
| 3.5 | Custom Analysis and Professional Services: Provide optional specialized analyses, reports, or consulting services beyond standard platform functionality. |
| 3.6 | Custom POI and Geographic Boundary Support: Assist with creating, importing, modifying, or troubleshooting custom geographic areas. |
| 3.7 | Reporting and Presentation Support: Assist with developing reports, visualizations, or presentation materials using the platform's data. |
| 3.8 | Data Integration and API Services: Provide optional services for integrating analytical data with City systems or external applications. |
| 3.9 | Optional Third-Party Data and Data Enrichment: Provide additional datasets or analytical products beyond those included in the base subscription. |
| 3.10 | Technical Support and Maintenance: Provide ongoing software updates, troubleshooting, service support, and maintenance. |
| 3.11 | Additional Modules and Optional Services: Identify other available capabilities or services that may benefit the City. |
| 4 | Mandatory Technical Requirements |
| 4.1 | Vendor-Hosted Solution: The solution must be vendor-hosted and accessible through a currently supported web browser without requiring specialized City-owned server infrastructure. |
| 4.2 | Custom Geographic Area Support: The solution must support the creation and/or import of custom geographic areas and Points of Interest (POIs). |
| 4.3 | Data Export Capabilities: The solution must support exporting analytical results and reports in commonly used file formats. |
| 4.4 | Information Security Standards: The proposed solution must meet the City's specified cybersecurity framework requirements, including SOC 2 Type II or ISO/IEC 27001, as applicable. |
| 4.5 | Data Encryption: The solution must provide encryption of data at rest and in transit using the security standards identified in the RFP. |
| 4.6 | User Authentication and Access Controls: The solution must provide appropriate authentication and access controls for authorized City users. |
| 4.7 | Data Privacy and Protection: The solution must protect individual privacy and must not provide City users with personally identifiable information or the ability to identify individual devices or persons. |
| 4.8 | Third-Party Data Providers and Subprocessors: The proposer must disclose material third-party data providers or subprocessors and explain how privacy and security requirements are maintained. |
| 4.9 | Security Certification Documentation: The proposer must provide validation of any claimed security certifications applicable to the proposed solution. |
| 4.10 | API or Web Services Capabilities: The solution must provide the API and/or web services interface capabilities specified in the RFP. |
File details come from the government source that posted it. Updated .