CITY OF PETERSBURG, VIRGINIA

REQUEST FOR INFORMATION

RFI No. 127426

PROJECT TITLE: CLOUD-BASED ENTERPRISE RESOURCE PLANNING (ERP)

SYSTEM

ISSUE DATE: August 28, 2026

1. DEFINITIONS

Request for information is an informal document issued when the City is not aware of the products or services available in the market which may satisfy its requirements. An

RFI may result in the issuance of an IFB, or RFP after the City determines the types of products that are available which may satisfy its requirements. An RFI cannot be made into an agreement.

City means The City of Petersburg, and its officers, elected and appointed officials, employees, and agents.

Respondent means an individual, company, firm, corporation, partnership, or other entity that submits a response to the RFI.

Response means information submitted to the City by a Respondent pursuant to the

Request for Information.

2. SCHEDULE

RFI Issued August 28, 2026

Deadline for Questions September 8, 2026

Deadline for Responses September 15, 2026

3. PURPOSE

The City of Petersburg is issuing this Request for Information (RFI) seeking to initiate discussions and solicit information from qualified vendors regarding Cloud-Based

Enterprise Resource Planning (ERP) solutions suitable for use by a small to mid-sized municipal government.

The intent of this RFI is to gather information to assist the City in:

• Understanding available ERP solutions and deployment models.

• Refining functional and technical requirements.

• Assessing implementation approaches and estimated timelines.

• Identifying vendors available through cooperative purchasing contracts authorized under the Virginia Public Procurement Act.

• Evaluating the vendor’s long-term product roadmap, financial stability, commitment to innovation, and ability to support evolving municipal requirements.

4. BACKGROUND

The City of Petersburg currently utilizes the BAI ERP system to support its financial and administrative operations. The City is exploring a transition to a modern, cloud-based ERP system to improve system reliability, usability, security, and long-term sustainability.

5. SCOPE OF WORK/SPECIFICATIONS

A. Enterprise Platform Requirements

The City seeks a modern, cloud-based Enterprise Resource Planning (ERP) platform that provides a fully integrated suite of applications supporting fiscal management, human resources, payroll, utility billing, procurement, asset management, permitting, fleet management, reporting, and citizen-facing services.

The City has approximately 50 ERP users across Finance, Human Resources, and related administrative departments. The City desires a solution that is appropriately scaled for its size while providing robust municipal functionality.

The proposed solution should provide a single source of truth for organizational data, minimize duplicate data entry, automate manual processes, and support future growth.

The City prefers a solution that relies upon standard delivered functionality whenever possible while allowing configuration to meet local government operational requirements.

The solution should provide seamless integration among all modules and offer a consistent user experience across desktop and mobile environments.

The City prefers a configurable platform that minimizes custom programming and leverages industry-standard municipal best practices.

B. Financial Management

The City requires a comprehensive fiscal management solution capable of supporting governmental accounting and reporting requirements.

The proposed system should support:

• General Ledger

• Accounts Payable

• Accounts Receivable

• Budget Preparation and Budget Management

• Cash Management

• Fixed Assets

• Project and Grant Accounting

• Purchasing and Procurement

• Encumbrance Accounting

• Bank Reconciliation

• Comprehensive Financial Reporting

The solution should provide automated workflows, electronic approvals, audit trails, and configurable business rules for procurement and financial transactions. The City currently utilizes purchase approval workflows and expects improved automation and transparency within the new ERP environment.

The system should support real-time financial reporting and dashboards that allow executives, department directors, and finance staff to monitor expenditures, revenues, budgets, and financial performance.

C. Human Resources, Payroll, and Workforce Management

The City employs approximately 585 full-time employees and 171 part-time employees.

The City seeks a comprehensive Human Capital Management (HCM) solution that supports:

• Employee records management

• Position control

• Organizational management

• Recruiting

• Applicant tracking

• Onboarding

• Benefits administration

• Performance management

• Learning management

• Employee self-service

• Manager self-service

• Payroll processing

• Time and attendance integration

• Personnel action tracking

• Regulatory reporting

The City currently utilizes NeoGov for recruiting and onboarding functions and

TimeClock Plus for timekeeping. Vendors should identify how their solution would replace, integrate with, or coexist with these systems.

The proposed solution should support electronic workflow approvals, employee and manager self-service portals, and mobile access to workforce functions.

The solution should support electronic personnel files, document retention, position budgeting, succession planning, and workforce analytics.

D. Payroll Processing

The City requires a payroll system capable of supporting local government payroll administration, including multiple employee classifications, deductions, benefits, leave tracking, and reporting.

The City anticipates a transition period that may include parallel payroll processing and dual-entry validation during implementation. Vendors should provide recommendations for conversion, testing, and transition methodologies that minimize operational risk.

The solution should support:

• Automated payroll calculations

• Direct deposit

• Tax reporting

• Benefit deductions

• Leave accruals

• Payroll reconciliation

• Electronic earnings statements

• Regulatory compliance reporting

E. Utility Billing and Customer Information Management

The City operates utility services for approximately 12,000 customer accounts and provides water, wastewater, stormwater, and refuse services. Utility bills are issued monthly. The City currently utilizes Itron Temetra for meter-related operations.

The proposed utility billing solution should support:

• Customer account management

• Meter management

• Consumption tracking

• Billing and collections

• Service order management

• Delinquency processing

• Payment processing

• Customer self-service portals

• Mobile access

• Revenue analytics

The system should integrate with online payment processing platforms and support batch payment processing procedures utilized by the City.

The City seeks to streamline utility operations while improving customer service and reducing manual processing.

F. Asset Management and Work Order Management

The City maintains approximately:

• Ninety-two facilities

• 341 fleet vehicles

• 701 streets

• Utility infrastructure serving approximately 12,000 accounts

The City currently processes approximately 1,200 work orders annually.

The proposed asset and work management solution should support:

• Asset lifecycle management

• Preventive maintenance

• Corrective maintenance

• Work order management

• Mobile workforce management

• Inventory control

• Asset condition assessments

• Capital planning

• GIS integration

• Reporting and analytics

The solution should support administrative users, operational users, mobile field staff, and work request submitters through role-based security.

The City seeks a solution that improves maintenance planning, asset reliability, regulatory compliance, and operational visibility.

Vendors should identify whether GIS functionality is native, embedded, or delivered through third-party integrations.

G. Fleet Management

The City maintains approximately 341 vehicles and equipment assets.

The proposed fleet management capabilities should support:

• Vehicle inventory

• Preventive maintenance scheduling

• Fuel management

• Equipment tracking

• Repair history

• Driver assignments

• Parts inventory

• Fleet utilization analytics

• Replacement planning

Fleet management capabilities should be integrated with procurement, inventory, finance, and asset management modules.

H. Procurement and Contract Management

The City seeks enhanced procurement functionality that supports transparency, accountability, and compliance.

Required capabilities include:

• Requisition management

• Electronic purchase approvals

• Purchase order processing

• Vendor management

• Contract management

• Bid management

• Procurement reporting

• Budget control verification

The solution should automate approval workflows and provide electronic audit trails.

I. Permitting and Community Development

The City manages multiple permit types including right-of-way permits, special event permits, driveway entrance permits, work-in-street permits, and related public works permitting activities. The City processes 60 to 70 permits annually.

The proposed solution should support:

• Permit application processing

• Workflow automation

• Electronic review routing

• Fee calculation

• Inspection management

• Public portal access

• Online application submission

• Reporting and analytics

The City is interested in solutions that improve efficiency for both staff and citizens.

J. Code Enforcement and Violations Management

The City issues 1,400 to 1,500 annual grass and property maintenance citations.

The solution should support:

• Complaint intake

• Case management

• Inspections

• Citation processing

• Enforcement tracking

• Mobile inspections

• Reporting and dashboards

• Approximately 300 miscellaneous AR invoices per month

The City seeks improved visibility into enforcement activities and case resolution timelines.

K. Revenue Management and Tax Administration

The City generates approximately:

• 13,500 annual real estate tax bills

• 22,000 annual personal property tax bills

The City operates under a single Tax Identification Number (EIN).

The solution should support:

• Property tax administration

• Collections management

• Billing and receivables

• Delinquency processing

• Payment integration

• Revenue forecasting

• Citizen self-service

Vendors should identify whether these functions are delivered through native functionality, strategic partnerships, or third-party integrations.

L. Reporting, Analytics, and Executive Dashboards

The City requires robust reporting capabilities across all functional areas.

The proposed solution should provide:

• Ad hoc reporting

• Standard reports

• Financial statements

• Operational dashboards

• Executive scorecards

• Budget reporting

• KPI tracking

• Data exports

The City expects real-time visibility into operational and financial performance.

Examples include:

• Financial performance dashboards

• Budget-to-actual reporting

• Utility consumption analytics

• Work order completion metrics

• Payroll and workforce analytics

M. Data Conversion and Historical Records

The City currently maintains approximately 25 years of historical information within its existing ERP environment.

Vendors should provide detailed recommendations for:

• Data conversion methodology

• Data cleansing

• Archival strategies

• Historical reporting access

• Validation and reconciliation procedures

The City desires the maximum practical retention of historical data while balancing implementation cost, risk, and project timeline.

N. Enterprise Integration Requirements and Architecture

The City seeks an ERP solution that serves as the authoritative enterprise platform for financial, operational, asset management, utility billing, payroll, procurement, and workforce information while maintaining seamless integration with both internal and external business systems.

The proposed solution shall provide a modern, secure, and scalable integration architecture that supports the exchange of information through industry-standard APIs, web services, middleware technologies, and other configurable integration methods. The solution should be designed to minimize duplicate data entry, eliminate data silos, and enable real-time or near real-time access to critical business information across departments.

At a minimum, the proposed ERP platform must support integration with online payment platforms, banking institutions, timekeeping systems, meter reading systems, Geographic

Information Systems (GIS), document management systems, and third-party reporting and analytics tools.

The City’s objective is to establish an integrated technology ecosystem that allows business processes to flow seamlessly across functional areas while ensuring the accuracy, consistency, and accessibility of enterprise data.

Vendors should clearly describe their integration framework and identify whether proposed interfaces are delivered through native functionality, configurable integrations, partner-supported solutions, custom development, batch processing, or real-time communication methods.

Vendors shall identify all standard interfaces currently available and distinguish between included integrations and integrations requiring additional licensing, software, middleware, professional services, or third-party products.

Additionally, vendors should explain how their integration architecture supports future expansion, system interoperability, workflow automation, data governance, cybersecurity requirements, and long-term operational sustainability.

Architectural Principles

The City expects the proposed ERP platform to support the following architectural principles:

Single Source of Truth

The ERP solution should serve as the system of record for core financial, payroll, procurement, budgeting, asset management, and operational data.

The architecture should minimize redundant data storage and maintain consistency across integrated systems.

Open Integration Framework

The solution should provide open integration capabilities including:

• REST APIs

• SOAP-based web services where necessary

• Secure file transfer mechanisms

• Middleware compatibility

• Event-driven integrations

• Data import and export utilities

The City prefers standards-based integration methods that avoid vendor lock-in and support future technology initiatives.

Secure Data Exchange

All integrations should utilize encrypted communication protocols and support modern cybersecurity standards.

The architecture should provide:

• API authentication

• Multi-factor authentication support

• Role-based security controls

• Audit logging

• Data encryption in transit and at rest

• Error monitoring and notification capabilities

Scalability

The integration architecture should be capable of supporting future business systems, increased transaction volumes, additional departments, expanded utility operations, and future smart-city initiatives.

Enterprise Systems Requiring Integration

The City anticipates integration requirements with the following systems at implementation or shortly thereafter.

Time and Attendance Systems

The ERP solution should support integration with workforce management and timekeeping systems, including TimeClock Plus or replacement solutions.

Integration should support:

• Employee records

• Time entry

• Leave balances

• Payroll processing

• Labor distribution

• Overtime calculations

The City prefers automated interfaces that eliminate manual payroll data entry.

Human Resources Systems

The City currently utilizes NeoGov for recruiting and onboarding functions.

Vendors should describe:

• Native HR capabilities

• Integration options with NeoGov

• Data synchronization methods

• Applicant and employee record transfers

The City is interested in understanding whether proposed solutions replace, integrate with, or augment current HR applications.

Utility Systems

The City currently utilizes Itron Temetra meter-reading technology.

The proposed architecture should support:

• Meter reading imports

• Consumption updates

• Customer account synchronization

• Billing calculation support

• Service order exchanges

The City prefers automated data exchanges with minimal manual intervention.

Online Payment Platforms

The ERP solution should integrate with current and future payment processing providers.

Integration capabilities should support:

• Utility payments

• Tax payments

• Permit payments

• Miscellaneous receivables

• Payment reconciliation

The City currently processes payment transactions through batch processing procedures and seeks opportunities to streamline reconciliation processes while maintaining strong financial controls.

Financial Institutions and Banking Systems

The proposed solution should support integration with banking partners for:

• Positive Pay

• ACH processing

• Wire transfers

• Electronic funds transfer

• Automated bank reconciliation

• Cash management reporting

The City seeks automated banking interfaces that reduce manual processing and improve cash visibility.

Geographic Information Systems (GIS)

The City expects vendors to support integration with GIS platforms where applicable.

Potential use cases include:

• Utility infrastructure management

• Asset location tracking

• Work order management

• Permit management

• Property information management

The City prefers GIS-enabled workflows that improve operational efficiency and decision-making.

Document Management Systems

The ERP solution should support integration with electronic document management solutions.

Integration should allow:

• Document storage

• Invoice imaging

• Contract management

• Supporting documentation retention

• Permit and project documentation

The City seeks to reduce paper-based processes and improve document accessibility.

Fleet and Asset Management Systems

Integration architecture should support data sharing between:

• Asset management

• Fleet management

• Purchasing

• Inventory control

• Preventive maintenance

• Fiscal management

The City seeks comprehensive visibility into lifecycle costs associated with assets and fleet operations.

Data Integration Requirements

The City expects the vendor to provide a comprehensive data integration strategy addressing:

Real-Time Data Processing

Where operationally beneficial, the solution should support real-time integration for:

• Employee information

• User authentication

• Utility account updates

• Work order status updates

• Procurement approvals

Batch Processing

The solution should also support scheduled processing for:

• Financial transactions

• Utility payment imports

• Vendor data synchronization

• Historical data synchronization

The City currently utilizes certain batch-processing workflows, including payment processing operations. Vendors should identify opportunities for automation while preserving required business controls.

Master Data Management

The proposed solution should provide a framework for managing key enterprise data elements, including:

• Customers

• Citizens

• Vendors

• Employees

• Assets

• Utility accounts

• Properties

• Financial chart of accounts

The City seeks to maintain consistent data standards across all integrated systems.

Reporting and Analytics Architecture

The integration architecture should support enterprise reporting and business intelligence capabilities.

The proposed solution should provide:

• Consolidated reporting across modules

• Executive dashboards

• Data warehouse compatibility

• Self-service reporting

• Business intelligence integrations

The City seeks near real-time visibility into financial, operational, utility, workforce, and asset performance metrics.

Conversion and Historical Data Architecture

The City currently maintains approximately twenty-five years of historical information within its legacy ERP environment. Vendors should describe the recommended approach for migrating, archiving, and providing access to historical records.

The proposed architecture should support:

• Historical transaction preservation

• Audit record retention

• Historical reporting

• Legacy data accessibility

• Long-term records management

Future-State Integration Vision

The City's long-term objective is to establish an integrated digital government platform where financial, operational, workforce, utility, asset, permitting, and citizen service functions operate within a unified technology environment.

Vendors should describe how their proposed solution supports:

• Enterprise-wide workflow automation

• Citizen self-service capabilities

• Mobile workforce enablement

• Artificial intelligence and analytics capabilities

• Cloud-native architecture

• Future application integration

• Smart-city initiatives

• Continuous process improvement

The City encourages vendors to propose innovative integration strategies that leverage industry best practices while minimizing implementation complexity, ongoing maintenance requirements, and total cost of ownership.

O. Security, Compliance, and Auditability

The City requires enterprise-grade security controls including:

• Role-based security

• Multi-factor authentication

• Audit logging

• Data encryption

• Segregation of duties

• Compliance reporting

• Disaster recovery capabilities

Cloud Hosting Requirements

• SOC 1 Type II

• SOC 2 Type II

• Annual penetration testing

• Data residency information

• Disaster recovery objectives

• Recovery Time Objective (RTO)

• Recovery Point Objective (RPO)

Cybersecurity Requirements

• Single Sign-On (SSO)

• Microsoft Entra ID integration

• Multi-factor authentication

• Conditional Access support

• Security event logging

• Security monitoring tools

The solution should provide complete transaction audit trails and support financial and regulatory audits.

P. Implementation Expectations

The City is open to either a phased implementation approach or a broader enterprise deployment strategy, depending on vendor recommendations and project risk considerations.

The City anticipates a transition period during which certain functions, particularly

Accounts Payable and Payroll, may operate in parallel between legacy and new systems before full migration is achieved.

Vendors should provide:

• Recommended implementation methodology

• Project governance structure

• Conversion strategy

• Change management approach

• Training methodology

• Resource requirements

• Risk mitigation strategies

• Go-live recommendations

Q. Organizational Change Management

Request vendors must describe:

• Executive sponsorship strategies

• Change management methodology

• Communication planning

• End-user adoption programs

• Super-user training approach

Particular emphasis should be placed on minimizing disruption to City operations while maximizing user adoption and long-term return on investment.

R. Artificial Intelligence and Process Automation

The City is interested in understanding how vendors are leveraging artificial intelligence, machine learning, robotic process automation, predictive analytics, and digital assistants within their ERP platform.

Vendors should describe:

• AI-enabled reporting

• Forecasting capabilities

• Predictive maintenance

• Intelligent workflow routing

• Automated document processing

• Natural language search

• Copilot-style functionality

• Future AI roadmap

6. ANTICIPATED PROCURMENT PATH

Following review of responses to this RFI, the City anticipates proceeding using one of the following procurement approaches, subject to internal approvals:

• Cooperative purchasing through an existing contract competitively awarded by another public body and authorized for cooperative use under § 2.2-4304 of the Virginia Public

Procurement Act; or

• Issuance of a formal Request for Proposals (RFP) by the City.

Responses to this RFI will inform, but will not determine, the City’s final procurement approach.

7. SCOPE OF INFORMATION REQUESTED

Vendors are requested to provide high-level, non-binding information addressing the areas below. Detailed technical proposals are not required.

A. Vendor Overview

• Company name and headquarters location.

• Years of experience providing ERP systems to local governments.

• Approximate number of municipal ERP clients.

• Experience with Virginia cities or counties (if applicable).

B. ERP Solution Overview

• Name and version of proposed ERP solution(s).

• Cloud deployment model (SaaS, hosted, or hybrid).

• Description of core system architecture.

• Summary of cybersecurity and data protection standards (e.g., SOC 2).

C. Functional Capabilities

Please indicate whether the following functions are available as part of the solution:

• General Ledger

• Budgeting

• Purchasing

• Accounts Payable

• Fixed Asset Accounting

• Project and Grant Management

• Human Resources

• Time Entry

• Payroll

• Utility Billing

• Planning

• Permitting and Inspections

• Code Enforcement

• Asset Management

• Work Orders

• Facilities Management

• Fleet Management

• Tax Assessment – Real Estate and Personal Property

• Tax Assessment – Business License, Income, and Misc. Taxes

• Tax Billing

• Accounts Receivable and Collections

• Cash Receipts

• Computer-Assisted Mass Appraisal

• Reporting and Analytics

Vendors may identify additional functions commonly used by municipal governments.

D. Implementation Approach

• Typical implementation timeline for a city with approximately fifty users.

• Overview of implementation methodology.

• Data migration approach, including experience migrating from legacy ERP systems.

• Training and change-management support provided to customers. This would include operating the legacy system and the new system concurrently for one year.

E. Support and Maintenance

• Description of customer support model.

• Hours of support and escalation procedures.

• Approach to system upgrades and enhancements.

• Availability of Virginia-based or regional support resources (if applicable).

F. Cooperative Contract Information

Vendors are requested to identify any existing cooperative contracts under which their

ERP solution is currently available to local governments, including:

• Contracting agency or cooperative organization

• Contract number and expiration date.

• Confirmation that Virginia cities may utilize the contract.

• Scope of services included under the contract.

G. Budgetary Information (Non-Binding)

To assist with planning purposes only, vendors may provide budgetary estimates, including:

• Typical one-time implementation costs

• Typical annual subscription or licensing costs

• Key factors that influence total cost of ownership

All cost information submitted in response to this RFI is considered non-binding.

8. PROPOSAL SUBMISSION INSTRUCTIONS

8.1 Submission Deadline: Responses shall be submitted to the City no later September 15, 2026, at 2:30 P.M. EST.

8.2 Delivery Method

Responses may be submitted electronically through eVA or by U. S. Mail, overnight service, or hand delivery.

A. Electronically through eVA

For guidance on how to submit a response, go to https://eva.virginia.gov/supplier-training-materials.html and select the "Respond to IFBs-RFPs and more" PDF located under the heading "Find and Respond to Virginia Business Opportunities (VBO)". If the Respondent determines that part or parts of its proposal are trade secrets or proprietary information that is not to be open to public inspection, the Respondent must submit an additional copy of its response that eliminates such part or parts. This copy shall be identified with the words "REDACTED COPY".

B. U. S. Mail, overnight service, or hand delivery

All responses must be sealed and labeled on the outside of an opaque envelope or package to show the following:

a. Title of Proposal

b. Name of Respondent

c. Address of Respondent

d. RFI Number

e. Receipt and Closing Date

Respondents shall submit one (1) electronic copy of the signed response on a USB Jump

Drive and one (1) original and five (5) hardcopy of the response to the City by mail or hand delivered. The Response shall be addressed to the following address:

City of Petersburg - Procurement Office

125 N. Union Street

Petersburg VA 23803

RFI # 127426

8.3 Questions and Agenda

All communications relating to this solicitation must be emailed to Eunita S Wade at purchasing@petersburg-va.org. For a question to be considered, the subject line of the email must state the following: RFI #127426. All questions must be submitted by

September 8, 2026, at 12:00 P.M. EST. No questions will be considered if they are received after that date/time. If any questions or responses require revisions to this solicitation, such revisions will be by addendum only.

Direct contact with City staff, representatives, and/or agents other than the Procurement mailto:purchasing@petersburg-va.org

Office is expressly prohibited except with the prior knowledge and permission of the

Procurement Office.

8.4 Response Format

Proposals shall be prepared simply and economically, providing a straightforward, concise description of capabilities to satisfy the requirements of the RFI. A Response submitted pursuant to the RFI shall include each of the following items in the order in which they appear below. Each item shall be clearly labeled, with pages numbered, and separated by tabs.

1. Title Page

a. The RFI title and number;

b. The Respondent's name, address, telephone number;

c. The name and email address of the Respondent's authorized contact person with respect to the Response; and

d. The date of preparation of the Response

2. Table of Contents

The Table of Contents shall indicate the material included in the Response by tab and page number. The Table of Contents shall mirror the format set forth in this section and shall include all the items set forth below.

3. Tab I, Statement of Interest

The Respondent shall provide a statement of interest explaining the Respondent's interest in providing an RFI to the City, the Respondent's willingness and ability to accommodate the requirements of the City.

4. Tab II, Qualifications and Experience

Description of company’s qualifications and experience with ERP systems to local governments, approximate number of municipal ERP clients, and experience with Virgiina cities or counties (if applicable) .

5. Tab III, Management Team

Discuss the qualifications of key staff members that will be assigned to the project.

6. Tab IV, ERP Solution Overview

a. Name and version of proposed ERP solution(s), cloud deployment model

(SaaS, hosted, or hybrid

b. Description of core system architecture

c. Summary of cybersecurity and data protection standards (e.g., SOC 2)

7. Tab V, Functional Capabilities

Per Section 4., C.

8. Tab VI, Implementation Approach

Overview of implementation approach, including data migration and training

9. Tab VII, Support and Maintenance

Description of customer support model, hours of support and escalation procedures

Approach to system upgrades and enhancements

Availability of Virginia-based or regional support resources (if applicable)

10. Tab VIII, Cooperative Contract Information

Vendors are requested to identify any existing cooperative contracts under which their ERP solution is currently available to local governments, including:

a. Contracting agency or cooperative organization

b. Contract number and expiration date, including, scope of work, terms and conditions

c. Conformation that Virginia cities may utilize contact

11. Tab VIX, Budgetary Information (Non-Binding)

Vendors may provide budgetary estimates, including:

a. Typical one-time implementation costs

b. Typical annual subscription or licensing costs

c. Keys factors that influence total cost of ownership

8.5 Conditions and Limitations

This Request for Information does not represent a commitment or offer by the City of

Petersburg to enter into an agreement with a respondent, or to pay monies or costs incurred in the preparation of a response to this request. The City is not obligated to contact the respondents in regard to the responses submitted, to use the information provided by the respondents, or to return the responses to the individual respondents.

Responses to this RFI will not be considered a response to any future RFP. A competitive solicitation may be issued at a later date.

The City reserves the right to amend this RFI or to cancel this process, in whole or in part, at any time.

8.6 Presentations/Demonstrations

In order to develop a more comprehensive understanding of the information submitted by a Respondent, the City may invite certain Respondents to make presentations and/or participate in face-to-face or telephonic conversations.