Property Data Services

The vendor is required to provide property data services for research efforts on valuation for right-of-way purchases or any property data require staff to utilize multiple tools and data sources to conduct research piece-meal in an incomplete and time-consuming process.
- Functional system requirements
•    System uses robust processes to identify and collect data on all property parcels in the city across multiple data sources.
•    System can integrate data from an unlimited number of city data sources
•    Ability to add additional ad hoc data relevant to the city into the system that is not currently in another system 
•    Property data must include, at minimum, parcel number, address (if applicable), information regarding buildings on the property, sale and transfer history including cost, type of sale or transfer, property valuation information.
•    Property ownership information is sourced from multiple sources and consolidated. 
•    Property ownership data must include, at minimum, owner type, name, contact information.
•    System integrates property data across all sources such that all required information regarding a parcel is accessible in one location.
•    Property information is accessible through address search, map views, and criteria search functions. 
•    Data for all property owned by the same entity can be accessed through the system. 
•    Automated valuation modeling to assess property pricing for right-of-way acquisitions. 
•    Ability for users to drill directly into a desired property from a view or map where they can access information such property data, sales history, and ownership information. 
•    Ability to access data system from any browser on both desktops and mobile devices. 
•    Ability to use mobile device location to view nearby properties, including the ability to pair location information with search criteria to identify specific types of properties that are nearby. 
•    Ability to download lists of properties in a spreadsheet, e.g., all those that meet certain search criteria or all owned by the same entity. 
•    Ability to save search criteria and search results for later retrieval. 
•    The city will retain full access and control of all datasets even if the city ends this contract and migrates to a different platform. 
•    The data will be made readily available to the city in a manner useable by our current systems. 
•    System should be device agnostic, providing full functionality for each device. 
•    Ability to provide automatic import of data from other city systems through standard APIs and Boomi middleware
•    Ability to publish data and reports to various audiences - public and internet, within the organization, etc.
•    Ability to share reports directly from the system with individual users by email or publish externally
•    Ability to integrate easily with GIS and handles Esri GIS formats for mapping data
•    Ability to export GIS data in multiple standard file formats
•    Ability to search all contents (global search).
•    Ability to narrow the search results with filtering i.e., area, owner, etc.
- Technical system requirements
•    City data gathered in this system must remain isolated from other customers. we do not allow our data to be mixed into the same database or other systems with other customers.
•    Ability to provide real-time remote-control support of the application through a vendor provided remote desktop support software (i.e., skype, WebEx, go-to meeting, teams etc.).
•    Vendor has the ability to provide redundancy to ensure maximized up time.
•    Database backed up on a regular basis (detail in the comments area).
•    Solution should utilize best practice system recovery in the event of a loss.
•    Offer a user interface which is native to the application, that can be accessed using most recent version of edge, google chrome, Firefox, safari, etc. and be backward compatible to at least three previous version(s).
•    The solution must accommodate individuals with disabilities in accordance with the act.
•    System must provide group and user security.
•    Application administrator can manage security, maintenance tables, user logins and access.
•    supports multiple concurrent users accessing the system at once (detail if there are any limits to the number of users in the system at the same time editing the same item).
•    "All standard user accounts for the system should be maintained within the city’s active directory environment to ensure adherence to the city’s password policy and account management standards and processes. 
•    The system must either use SAML 2.0 single sign on (SSO) or authenticate users directly with active directory (if the system being proposed in hosted on premise). 
•    Online screens must be fully compatible with latest operating systems (see technical environment)
•    Always able to use the most up to date software with minimal “down time” for new upgrades and features which should be implemented as part of regular vendor support services.
•    Flexible scheduled maintenance windows that limit down time (detail in the comments area).
•    The system provides for version change control to maintain updated information for modification support purposes – whether vendor or self-hosted.
•    There is a provision for non-technical, complete, and easy-to-read user documentation, including reports, online functions, screen illustrations, data entry requirements and diagrams of table links.
•    The system provides online help features at all screen levels.
•    The system offers industry standard backup and retrieval processes.
•    Database used to store the city’s data must be ODBC (open data base connectivity) compliant, allowing the city to access and report on its data.
•    Vendor sends communications regarding software enhancements, bug fixes, new releases, and 
•    Occur via email, newsletter, or system notifications.
•    All requirements listed in section “technical environment” where applicable.
•    Provide database table layout with primary and foreign keys
•    System must provide test environment and production environment
•    The system must use encryption standards such as aes-256 for all data at rest. 
•    The system must use encryption using TLS 1.2 and 1.3 or equivalent protocols for data in transit. 
•    The data must be stored and processed within the continental united states, ensuring compliance with local data residency and sovereignty laws.
•    The system can integrate with our security information and event management (SEIM) solution for continuous monitoring. 
•    The system must store detailed logging of access and activity with tamper-evident logs for a minimum of a year.

- Non-Mandatory Pre-Proposal Meeting Date: October 9, 2025
- Questions/Inquires Deadline: October 9, 2025