RFP 26-4972 REAL-TIME FLOOD FORECASTING (RTFF) SOFTWARE SOLUTION

SOLICITATION COVER SHEET
SOUTHWEST FLORIDA WATER MANAGEMENT DISTRICT REQUEST FOR PROPOSALS
SUBMIT PROPOSALS TO: SOUTHWEST FLORIDA WATER MANAGEMENT DISTRICT
VIA: WWW.DEMANDSTAR.COM
DIRECT INQUIRIES TO: Chamanda Burris, Senior Procurement Specialist
PHONE: 352-505-2970 E-mail: procurement@watermatters.org
DATE POSTED: PROPOSALS ARE DUE AND WILL BE PUBLICLY OPENED:
August 21, 2026 September 15, 2026, at 2:00 p.m., and may not be withdrawn for 120 days after
this date.
PRE-PROPOSAL CONFERENCE: Not Applicable
ORAL DEMONSTRATIONS: October 22 & 23, 2026
TITLE: RFP 26-4972 REAL-TIME FLOOD FORECASTING (RTFF) SOFTWARE SOLUTION
SPECIFICATIONS: The Southwest Florida Water Management District (District) is soliciting proposals from
qualified software vendors for a configurable SoftwareasaService (SaaS)based RealTime Flood
Forecasting (RTFF) solution. The RTFF system will support predictive flood analysis by integrating forecasted
rainfall, waterlevel data, and current hydrologic conditions to anticipate potential flooding scenarios.
Reason for No-Bid
Respondent Name:
Mailing Address:
City-State-Zip:
Telephone Number ( ) - FAX Number ( ) - Toll-Free Number ( ) -
Email address for correspondence:
Authorized Signature:
Full Name (please print or type):
Title (please print or type):
I, the above signed, as Respondent, hereby declare that I have carefully read this Request for Proposal and
its provisions, terms, and conditions covering the equipment, materials, supplies, or services as called for,
and fully understand the requirements and conditions. I certify that this proposal is made without prior
understanding, agreement, or connection with any corporation, firm, entity, or person submitting a proposal
for the same goods/services (unless otherwise specifically noted) and is in all respects fair and without
collusion or fraud. I agree to be bound by all the terms and conditions of this Request for Proposal and certify
that I am authorized to sign this proposal for the Respondent.
THE DISTRICT OFFICIALLY POSTS SOLICITATION PACKAGES ON WWW.DEMANDSTAR.COM AND
WWW.WATERMATTERS.ORG/PROCUREMENT. THE DISTRICT RECEIVES PROPOSALS THROUGH
DEMANDSTAR AT WWW.DEMANDSTAR.COM. THE DEMANDSTAR TIME STAMP WILL BE
CONCLUSIVE AS TO THE TIMELINESS OF FILING. IT IS THE RESPONDENT'S RESPONSIBILITY TO
ENSURE THAT ITS PROPOSAL IS TIMELY UPLOADED. PROPOSALS RECEIVED AFTER THE DATE
AND TIME SPECIFIED WILL NOT BE ACCEPTED. TO MAINTAIN A SECURED SEALED PROCESS
ELECTRONIC SUBMISSIONS MAY BE MADE ONLY THROUGH THE DEMANDSTAR PLATFORM.
FAXES, EMAILS, OR HAND DELIVERY WILL NOT BE ACCEPTED.
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 1 of 45

SOUTHWEST FLORIDA WATER MANAGEMENT DISTRICT
REQUEST FOR PROPOSALS 26-4972
REAL TIME FLOOD FORECASTING SOFTWARE SOLUTION
TABLE OF CONTENTS
PART I - GENERAL CONDITIONS
1.1 Purpose PART II - INTRODUCTION
1.2 Definitions 2.1 Background Information
1.3 Development Cost 2.2 Term of Contract
1.4 Changes, Delays, and Addenda 2.3 Proposal Calendar
1.5 Pre-Proposal Conferences
1.6 Rules for Proposals PART III - NATURE OF SERVICES REQUIRED
1.7 Proposal Format 3.1 Project Objectives
1.8 Proposal Opening 3.2 Scope of Work
1.9 Questions 3.3 Annual Rate
1.10 Conflict of Interest 3.4 Deliverables
1.11 Proposal Withdrawal
1.12 Public Availability of Records PART IV - INSURANCE
1.13 Responsive/Responsible 4.1 Insurance Requirements
1.14 Right to Accept or Reject Proposals
1.15 Notice of Intent to Award PART V - EVALUATION PROCEDURES
1.16 Protests 5.1 Review of Proposals and Preliminary
1.17 Contract Information Evaluation
1.18 Indemnification 5.2 Software Demonstrations
1.19 Withholding Payment 5.3 Final Evaluation and Negotiations
1.20 Termination 5.4 Evaluation Method and Criteria
1.21 Law Compliance 5.5 Final Selection
1.22 Americans with Disabilities Act (ADA)
1.23 Public Entity Crimes ATTACHMENTS
1.24 Discrimination Attachment 1 Reference Form
1.25 Responsible Vendor Determination Attachment 2 Supplemental Information
1.26 Scrutinized Companies Questionnaire
1.27 Correspondence Attachment 3 Sample Agreement
1.28 Background Checks Attachment 4 Sample Mutual Non-Disclosure
1.29 Purchases by Other Public Agencies Agreement
1.30 Employment Eligibility Verification Attachment 5 Sample Affidavit for No Use of
1.31 No Use of Coercion for Labor or Services Coercion for Labor or Services
1.32 Contracting with Entities of Foreign Concern
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 2 of 45

PART I - GENERAL CONDITIONS
1.1 PURPOSE. The purpose of this solicitation is to provide guidelines for submission of proposals
for the services described in Part III, hereinafter referred to as the "Services."
1.2 DEFINITIONS. "Respondent" means consultant, contractor, organization, firm, college or
university, or other entity submitting a response to this solicitation. "District" means the
Southwest Florida Water Management District, which is the issuing agency.
1.3 DEVELOPMENT COST. Neither the District nor its representatives will be liable for any
expenses incurred in connection with the preparation of a response for this solicitation. All
proposals should be prepared simply and economically, providing a straightforward and concise
description of the Respondent's ability to meet the requirements of the solicitation.
1.4 CHANGES, DELAYS, AND ADDENDA. The District reserves the right to delay scheduled
solicitation due dates if determined to be in the best interest of the District.
District solicitations, changes, delays, and addenda are available for review and download at
http://www.watermatters.org/procurement and www.demandstar.com. Persons/firms receiving
solicitations from the Internet websites are responsible to recheck the websites for any changes
or addenda.
All interpretations and supplemental instructions will be in the form of written addenda, including
District answers provided in response to SECTION 1.9, QUESTIONS, of this solicitation.
Respondents will acknowledge receipt of all addenda in their proposal.
No interpretation of the meaning of the specifications or other solicitation documents, nor
correction of any apparent ambiguity, inconsistency or error therein, will be made to any
Respondent orally. Prospective Respondents are advised that no other sources are authorized
to give information concerning, explaining, or interpreting solicitation documents. Any
information obtained from an officer, agent or employee of the District or any other person will
not affect Respondent's risks or obligations or relieve it from fulfilling any and all conditions of
the solicitation.
1.5 PRE-PROPOSAL CONFERENCES. A pre-proposal conference will not be held for this
solicitation.
1.6 RULES FOR PROPOSALS. Two or more firms may combine for the purpose of responding to
this solicitation providing that one is designated as "Prime" Respondent and the other as "Sub-
Respondent(s)". The signer of the proposal must declare that any person or entity with any
interest in the proposal, as a principal, is identified therein; that the proposal is made without
collusion; that it is, in all respects, fair and in good faith; and that the signer of the proposal has
full authority to negotiate for and bind the Respondent stated on the solicitation cover sheet.
1.7 PROPOSAL FORMAT. In order to assist the District's review process, proposals are to be
prepared utilizing the following format. The evaluation criteria are set forth in PART V -
EVALUATION PROCEDURES.
The cost/fee schedule containing all price information, must be submitted as a separate file from
any file(s) containing all non-price factors as identified in SECTION 1.7, PROPOSAL FORMAT.
1.7.1 Sign and Return the Solicitation Cover Sheet. The person signing the proposal must
be an authorized signatory of Respondent as demonstrated by such individual being
listed as an officer on the Florida Division of Corporations (Sunbiz.org) website or in
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 3 of 45

Respondent's Articles of Incorporation, or specifically authorized in a Board Resolution.
1.7.2 Table of Contents. This should include clear identification of the material by section and
page number.
1.7.3 Letter of Transmittal. The letter of transmittal should be no more than two pages in
length and must briefly demonstrate the Respondent's understanding of the required
work, along with a clear commitment to perform the services in a timely manner. It should
identify the individuals authorized to represent the organization, including their names,
titles, addresses, and telephone numbers. Additionally, the letter must disclose any
potential conflicts of interest in accordance with SECTION 1.10. CONFLICT OF
INTEREST, or affirm that none exist. The letter must be signed by an official authorized
to negotiate on behalf of the Respondent.
1.7.3.1 Organizational Profile and Qualifications. This section of the proposal
should provide the following:
1.7.3.2 A description of the Respondent's organization, including location(s), size,
range of activities, number of client organizations, current and projected
workloads, and any other appropriate information to describe the organization.
Emphasis should be given to the organization's relevant experiences with
similar projects to what is specified in the PART III - NATURE OF SERVICES
REQUIRED and expertise in the subject field; highlight history and experience
with other governmental entities. In addition, include answers to the following:
1.7.3.1 Name and address of operating company and contact, indicate type of
business (i.e. Individual, Partnership, Corporation, etc.)
1.7.3.2 Number of years in business, number of years as a provider of the services
specified in PART III - NATURE OF SERVICES REQUIRED, total number
of employees, number of people regularly employed as software
development/support consultants, and specifically, the number of people
regularly employed to provide the services specified in PART III NATURE OF
SERVICES REQUIRED.
1.7.4 Methodology and Approach.
1.7.4.1 Scope of Work. This section of the proposal must explain how the proposed
software meets the requirements outlined in SECTION 3.2, SCOPE OF
WORK.
1.7.4.2 Service Level Agreements. The Respondent must provide their Service Level
Agreements for response to District-reported problems and inquiries. Service
Level Agreements should include descriptions of issue severity levels,
response times, and resolution effort. Additionally, Respondents must specify
the hours of operation for support services and the location(s) of support
centers, list available support channels (e.g., email, phone, ticketing system,
knowledge base), and describe how District staff can access support tickets
and track their status. Include the escalation process if issues are unresolved.
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 4 of 45

1.7.4.3 System Availability. The Respondent must provide their Service Level
Agreements for system availability. The Respondent must provide system
availability statistics for the 12 months preceding the solicitation opening as
stated on the Solicitation Cover Sheet, along with any remediation actions
taken for not meeting the stated system availability.
1.7.4.4 Support Team Qualifications. The Respondent must provide information on the
qualifications required for a member of the proposed software's support team.
This includes length of experience, any required certifications, and any other
relevant information.
1.7.4.5 Implementation Plan. Provide an Implementation Plan that includes the
following as applicable: Proposed implementation tasks; project
communication strategy; typical implementation timeline from contract
execution to productive use with an existing model; resource needs, including
time required of District staff for implementation, organized by discipline (e.g.,
Engineering, Information Technology) or role (e.g., application administrator,
subject matter expert); and deliverables needed from District staff to efficiently
implement the software solution
1.7.4.6 Implementation Team Qualifications. The Respondent must provide
information on the qualifications required for members of the proposed
software's implementation team, unless no implementation team is needed
because the product is already implemented and fully functional. If an
implementation team is required, the Respondent must describe the
qualifications for team members, including length of experience, required
certifications, and any other relevant information.
1.7.4.7 District Staff Resource Needs. The Respondent must describe the expected
time commitment and skillsets required from District staff during
implementation and postdeployment, unless the product is commercial off the
shelf (COTS). If vendor implementation is required, the Respondent must
specify the anticipated level of effort and the necessary skillsets for District
staff.
1.7.4.8 System Requirements. Respondents must list any required or optional third-
party integrations (e.g., Microsoft 365) and associated documentation.
Respondent must also describe their plan for maintaining compatibility with
browser updates, and describe login security features. Respondents must also
list the hosting platform for the solution.
1.7.4.9 Training Plan. Respondents must provide a training plan for virtual delivery that
outlines the types of training offered and the estimated time commitments for
each user role (e.g., administrator, engineer/modeler). Specify whether
ongoing or refresher training will be available for new and existing users
throughout the contract term. Additionally, list any supplementary educational
resources, such as best-practice guides, webinars, virtual expert-led sessions,
searchable online documentation, or a knowledge base. It must also provide
high-level orientation sessions for certain members of District management.
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 5 of 45

1.7.4.10 Post Implementation Support. Respondents must provide periodic checkins
with the District's Project Manager, beginning with more frequent meetings
immediately after launch and transitioning to a regular schedule as the system
stabilizes. The frequency and method of these checkins will be determined by
mutual agreement between the District's Project Manager and the awarded
Respondent.
1.7.5 Security. The Respondent must describe how the confidentiality of District records and
data will be maintained, including a summary of current security procedures for
accessing, transmitting, and storing data. The Respondent also warrants that all
customer data will be stored and processed exclusively within the continental United
States.
All proposals must include the most recent SOC 2 Type II (or an equivalent certification)
report for the proposed Real Time Flood Forecasting Software Solution and all
associated service providers required for the proposed solution to operate as described
in the Scope of Work. This documentation must be uploaded as separate documents
from the proposal and pricing information.
Failure to include the required SOC 2 Type II report (or an equivalent certification) for the
solution and all associated service providers at the time of submittal may result in the
proposal being deemed non-responsive in accordance with SECTION 1.13,
RESPONSIVE/RESPONSIBLE.
Please also provide a statement identifying any additional security certifications held by
the proposed solution and all associated service providers. Additional documentation
may be requested.
1.7.5.1 Data Protection and Confidentiality. Respondents must explain how the
proposed solution will maintain the confidentiality of District records and data.
This includes:
* Security procedures currently in place for accessing, transmitting, and
storing data.
* Measures to prevent unauthorized access or disclosure.
* Disclose any past security breaches. If a security breach occurred, provide
the date of the breach, a brief explanation of the breach, and the
remediation steps.
* Describe your disaster recovery and business continuity practices.
* A statement confirming that all District data will be maintained and
processed exclusively within the continental United States.
1.7.6 References. Respondent must provide at least three separate, relevant, and verifiable
references, along with their contact information including phone number and email
address, for public entities that currently use the Respondent's proposed software
solution of similar size and scope as specified in PART III - NATURE OF SERVICES
REQUIRED. Each reference must be able to comment on Respondent's provided
software solution. References must be public entities of similar operations and size as
the District and have been using the software for at least one year.
It is highly recommended that each reference contact person be informed that they are
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 6 of 45

being used as a reference and that the District may be contacting them. Failure of
references listed to respond to the District's inquiries may negatively impact the
evaluation of the proposal, including rejection of the proposal as non-responsive.
References must be provided on the forms provided in Attachment 1, Reference Form.
1.7.7 Cost/Fee Schedule. The Respondent must submit all pricing information requested in
SECTION 3.3, ANNUAL RATE, as a separate file from all non-price proposal
documents.
1.7.8 Software Terms and Conditions Requirement. The Respondent must include with
their proposal any and all softwarerelated terms and conditions, license agreements,
subscription agreements, enduser license agreements (EULAs), service level
agreements (SLAs), dataprocessing or privacy terms, and any other contractual
documents that the District would be required to review, accept, or execute in order to
complete the purchase, implementation, or use of the proposed solution.
The District is under no obligation to review, negotiate, or accept any software terms,
conditions, or agreements submitted after the Notice of Intent to Award. Any terms
submitted after award may be rejected at the District's sole discretion.
1.7.9 Supplemental Information Questionnaire. Respondents must also provide responses
to Attachment 2 - Supplemental Information Questionnaire. Responses may be
provided in one of the following formats:
* Full responses written directly under each question in Attachment 2, or
* A crossreference indicating where in the proposal the answer to each question can
be found (section and page number must be clearly identified).
Respondents may copy the questions from Attachment 2 into their own formatted
document. If doing so, the document must be clearly titled 'Response to Attachment 2 -
Supplemental Information Questionnaire'.
Responses to Attachment 2 must be included with the Respondent's nonprice proposal
submission
1.7.10 Artificial Intelligence. The proposed solution may incorporate artificial intelligence (AI)
or machine learning; however, any AI components must operate transparently, use
verifiable data sources, and produce outputs that can be explained and validated by
District staff. Respondents must clearly identify any AI functionality included in their
product and outline associated data usage, privacy safeguards, and limitations; and
provide information requested in item 9 of Attachment 2, SUPPLEMENTAL
INFORMATION QUESTIONNAIRE. The AI solution should not use District data to
enhance the existing AI solution.
1.7.11 Submittal of Proposal Documents. In addition to the proposal submission
requirements listed in Subsections 1.7.1 through 1.7.11, all proposal documents and
forms listed below must be completely and accurately filled out, including a signature if
requested, and submitted with the proposal. Failure to do so may result in the rejection
of the proposal as non-responsive.
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 7 of 45

1.7.11.1 Forms required with proposal submission:
* Solicitation Cover Sheet: Respondent must sign and return the Solicitation
Cover Sheet with their proposal.
* Addenda Acknowledgement: Respondent must sign and return each
Addenda Acknowledgement with their proposal.
* Separate Cost/Fee Proposal Response.
* Additional Software Terms and Conditions as outlined in 1.7.8.
* Attachment 1 - Reference Form.
* Response to Attachment 2 - Supplemental Information Questionnaire.
* Most recent SOC 2 Type II report (or equivalent certification).
1.8 PROPOSAL OPENING. Proposal opening will be public on the date and at the time specified
in the solicitation. It is the Respondent's responsibility to assure that its proposal is uploaded to
DemandStar at the proper time. Proposals which are not uploaded by that time, for any reason,
will not be considered.
To be considered for evaluation, electronic files for all items identified in Section 1.7.12,
Submittal of Proposal Documents, must be uploaded to www.DemandStar.com no later than
the date and time specified on the Cover Sheet. Proposals not received in a timely manner by
DemandStar will not be accepted. THE DEMANDSTAR TIME STAMP WILL BE CONCLUSIVE
AS TO THE TIMELINESS OF FILING. THE DISTRICT HAS NO CONTROL OVER WHETHER
WWW.DEMANDSTAR.COM IS EXPERIENCING TECHNICAL DIFFICULTIES.
The District may make an award within 120 days after the date of the opening, during which
period responses shall remain firm and shall not be withdrawn. If an award is not made within
120 days, the response shall remain firm until either the District awards the Agreement or the
District receives, from the Respondent, written notice that the response is withdrawn. Any
response that expresses a shorter duration may, in the District's sole discretion, be accepted or
rejected.
AS INDICATED ON THE SOLICITATION COVER SHEET, THE DISTRICT RECEIVES
PROPOSALS THROUGH DEMANDSTAR. PROPOSAL PACKAGE DOCUMENTS MAY BE
ELECTRONICALLY SIGNED OR SIGNATURES TRANSMITTED ELECTRONICALLY (VIA
.PDF, ETC.). ELECTRONIC SIGNATURE/ TRANSMISSION SHALL BE DEEMED THE SAME
AS A HANDWRITTEN SIGNATURE/ORIGINAL EXECUTED COPY FOR THE PURPOSES
OF VALIDITY, ENFORCEABILITY, AND ADMISSIBILITY.
The District is providing a virtual option to join the proposal opening for RFP 26-4972, Real Time
Flood Forecasting Software Solution. The meeting will begin at the date and time specified on
the Cover Sheet. Respondents may view the opening by clicking on the "Join Microsoft Teams
Meeting" title below. You may also click on or copy and paste the following Teams link URL into
your browser:
Microsoft Teams meeting
Join on your computer or mobile app
Join the meeting now
Meeting ID: 222 275 741 075 49
Passcode: qy7tM6vg
https://bit.ly/4waIB9W
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 8 of 45

Dial in by phone
+1 786-749-6127,,403758549# United States, Miami
Phone conference ID: 403 758 549#
1.9 QUESTIONS. All questions must be presented in writing to Procurement@Watermatters.org,
or the physical address as stated in SECTION 1.27, CORRESPONDENCE and received by
the District no later than 5:00 p.m. on August 31, 2026. Inquiries must reference the proposal
title, number and the date of proposal opening. Respondents are responsible for checking the
District's website as specified in SECTION 1.4, CHANGES, DELAYS, AND ADDENDA, for the
District's responses to the questions presented. The District will attempt to answer all submitted
questions in a timely manner but accepts no responsibility for response delays.
1.10 CONFLICT OF INTEREST. The award hereunder is subject to the provisions of Chapter 112,
Part III, Florida Statutes, as amended, governing conflicts of interest. All Respondents must
disclose with their proposal the name of any officer, director, or agent who is also a public
employee. Further, all Respondents must disclose the name of any public employee who owns,
directly or indirectly, an interest of five percent (5%) or more in the Respondent's firm or any of
its branches.
The Respondent hereby agrees that, at the time of execution of an agreement, the Respondent
will not be involved in any matters which adversely affect any interest or position of the District,
and that the Respondent has no relationship with any third-party relating to any matters which
adversely affect any interest or position of the District. The Respondent will not accept during
the term of the agreement, or any renewal thereof, any retainer or employment from a third-
party whose interests appear to be conflicting or inconsistent with those of the District.
1.11 PROPOSAL WITHDRAWAL. Proposals may be withdrawn at any time prior to the opening via
the DemandStar platform.
1.12 PUBLIC AVAILABILITY OF RECORDS. Once opened, all proposals will become the property
of the District and, at the sole discretion of the District, may not be returned to the Respondent.
Any information, reports or other materials given to, prepared or submitted in response to this
solicitation will be subject to the provisions in Chapter 119, Florida Statutes, commonly known
as the Florida Public Records Act. Any Respondent claiming that its proposal contains
information that is exempt from the public records law must clearly segregate (separate
electronic copy PDF file) and mark that specific information as "CONFIDENTIAL", state the
reason such information is exempt from public disclosure, and provide the specific statutory
citation for such exemption (e.g., 119.0715, Florida Statutes): otherwise, Respondent waives
any possible or claimed exemption upon submission, effective at opening.
The Florida Public Records Act, section 119.071(1)(b), Florida Statutes, as amended, exempts
sealed proposals from inspection, examination, and duplication until such time as the District
issues a Notice of Intent to Award pursuant to section 120.57(3)(a), Florida Statutes, or within
30 days after the proposal opening, whichever comes first.
1.13 RESPONSIVE/RESPONSIBLE. At the time of submitting a proposal, the District requires that
the Respondent be properly licensed and registered to do business in the State of Florida in
accordance with applicable Florida Statutes. Responses that do not meet all requirements of
this solicitation or fail to provide all required information, documents, or materials as provided in
SECTION 1.7, PROPOSAL FORMAT, may be rejected as non-responsive. Respondents whose
responses, past performance, or current status do not reflect the capability, integrity or reliability
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 9 of 45

to fully and in good faith perform the requirements of the proposal may be rejected as non-
responsible. The District reserves the right to determine which responses meet the requirements
of this solicitation, and which Respondents are responsive and responsible. The District
reserves the right before awarding the proposal, to require a Respondent to submit such
evidence of their qualifications as it may deem necessary and may consider any evidence
available to it of the financial, technical and other qualifications and abilities of a Respondent to
perform the work in a satisfactory manner and within the time agreed upon. The Respondent is
assumed to be familiar with all federal, state or local laws, ordinances, rules and regulations that
in any manner affect the work, and to abide thereby if awarded the Agreement. Ignorance of
legal requirements on the part of the Respondent will in no way relieve responsibility.
1.14 RIGHT TO ACCEPT OR REJECT PROPOSALS. Proposals which are incomplete, conditional,
obscure, or contain additions not contemplated by the solicitation or irregularities of any kind, or
do not comply in every respect with the solicitation may be rejected as nonresponsive at the
option of the District. The District does not bind itself to accept the minimum specifications
stated in this solicitation but reserves the right to accept any proposal which, in the judgment of
the District, will best serve the needs and the interests of the District. The District reserves the
right to reject all proposals and not grant any award resulting from the issuance of this
solicitation. If awarded, no agreement will be formed between the Respondent and the District
until the agreement is executed by both parties.
1.15 NOTICE OF INTENT TO AWARD. The Notice of Intent to Award will be posted for review by
interested parties on the District's Internet website, (http://www.watermatters.org/procurement)
and www.demandstar.com.
1.16 PROTESTS. Any Respondent who protests the specifications or decision, or intended decision,
must file with the District a notice of protest and formal protest in compliance with Chapter
28-110, Florida Administrative Code (F.A.C.), and applicable provisions in section 120.57,
Florida Statutes. Failure to file a protest within the time prescribed in section 120.57(3), Florida
Statutes, will constitute a waiver of proceedings under Chapter 120, Florida Statutes.
1.17 CONTRACT INFORMATION. By submitting a proposal, the Respondent agrees to all the terms
and conditions of this solicitation and those attached as Attachment 3, Sample Agreement. The
contents of the proposal of the successful Respondent will be incorporated into a written
agreement in terms acceptable to the District at its absolute discretion. If a Respondent desires
to propose a change to a term or condition of the solicitation or of the Sample Agreement,
the Respondent must submit its request under the procedure set forth in SECTION 1.9,
QUESTIONS. Any changes to a term or condition of the solicitation or of the Sample Agreement
offered by a Respondent in a proposal will not be considered by the District. The submittal of a
proposal will constitute acknowledgement of all terms and conditions of this solicitation and
Sample Agreement, and the District will construe the proposal as though no changes were
presented. If Respondent desires an additional agreement(s) be considered for execution along
with the District's Agreement (Attachment 3, Sample Agreement), the Respondent must provide
a copy of the proposed agreement(s) with its response as indicated in SECTION 1.7.9, Software
Terms and Conditions Requirement. The District reserves the right to reject a Respondent if
the terms and conditions of a proposed agreement cannot be negotiated to the District's
satisfaction.
1.18 INDEMNIFICATION. The Respondent agrees to defend, indemnify and hold harmless the
District and all District agents, employees and officers from and against all liabilities, claims,
damages, expenses or actions, either at law or in equity, including attorney fees and costs and
RFP 26-4972 RTFF SOFTWARE SOLUTION August 21, 2026
Page 10 of 45