1. INTRODUCTION

1.1. Summary

Project Overview

The City of Daytona Beach seeks a qualified vendor to design and develop a modern mobile application that enhances civic engagement and streamlines access to public information. This initiative aims to transform how residents interact with City services by leveraging mobile, web, and emerging immersive technologies to deliver a seamless, user-friendly experience.

Scope of Work

The solution will consist of a cross-platform mobile application (Android and iOS), a web-based administrative portal, and a unified Supabase backend. Together, these components will enable real-time updates, secure data management, and intuitive interfaces for both residents and City staff. The platform will serve as a central hub for accessing services, submitting requests, and staying informed about community initiatives.

Vision and Impact

By modernizing service delivery and improving accessibility, this project will foster stronger community connections and empower residents to engage with their local government more effectively. Vendors with expertise in scalable architecture, responsive design, and innovative user experiences are encouraged to participate and help shape the future of civic technology.

1.2. Contact Information

Purchasing Purchasing

Purchasing Agent

301 S. Ridgewood Ave.

Daytona Beach, FL 32114

Email: purchasing@daytonabeach.gov

Phone: (386) 671-8082

Department:

Information Technology

1.3. Timeline

Release Project Date January 20, 2026 mailto:purchasing@daytonabeach.gov tel:(386)671-8082

Request For Proposal #2624RFP Title: 2624RFP - City of Daytona Beach Interactive Digital Platform

Pre-Proposal Meeting (Non-Mandatory) January 28, 2026, 11:00am

Join the meeting now

Meeting ID: 249 104 794 057 73

Passcode: MQ6hu3bP

Dial in by phone

+1 312-667-7230,,51504060# United States, Chicago

Phone conference ID: 515 040 60# https://teams.microsoft.com/meet/249104794057

73?p=TnAxWbB9XtvZ8KmoMN

Question and Request for Interpretation

Submission Deadline

February 10, 2026, 5:00pm

Proposal Submission Deadline February 17, 2026, 2:00pm

Join the meeting now

Meeting ID: 260 930 649 813 31

Passcode: 2aA3Dx37

Dial in by phone

+1 312-667-7230,,223054068# United States, Chicago

Phone conference ID: 223 054 068# https://teams.microsoft.com/meet/260930649813

31?p=8FeszNyWxNsbC5TX96

2. DEFINITIONS

THESE TERMS ARE STANDARD FOR ALL SOLICITATIONS ISSUED BY THE CITY OF DAYTONA BEACH. THE CITY

MAY DELETE, SUPERSEDE, OR MODIFY ANY OF THESE FOR A PARTICULAR SOLICITATION BY USE OF SPECIAL

PROVISIONS.

Certain terms used herein will have the following meanings. Note some defined terms are not relevant to this

Solicitation:

Addenda means written or graphic instruments issued prior to the end of the Offer Phase which clarify, correct, or change the Solicitation documents or Contract documents. Also means Addendum.

https://teams.microsoft.com/meet/24910479405773?p=TnAxWbB9XtvZ8KmoMN https://teams.microsoft.com/meet/24910479405773?p=TnAxWbB9XtvZ8KmoMN https://teams.microsoft.com/meet/26093064981331?p=8FeszNyWxNsbC5TX96 https://teams.microsoft.com/meet/26093064981331?p=8FeszNyWxNsbC5TX96

Bid means Solicitation Submission, or Proposal, submitted by a Bidder on the prescribed forms setting forth the prices for the work to be performed, and in the case of a Request for Proposals, the credentials, qualifications, and proposed project approach.

Bidder one who submits a response to a Solicitation; also means Proposer or Respondent.

City means The City of Daytona Beach, unless the context indicates otherwise, includes the City’s officers, employees, and agents.

Commodities means the supplies, materials, goods, merchandise, food, equipment, or other personal property, excluding real property, that the Bidder will be obligated to provide the City under any resulting Contract.

References to commodities shall mean goods.

Contract means the form Contract, if any, required by the City in order to integrate all terms and conditions therein, provided by the City for the Bidder’s execution and includes 1) the Solicitation documents 2) the Offer

Package, 3) the Resolution or Ordinance 4) all Purchase Orders issued pursuant to the Solicitation documents

5) all amendments that may after the date of award be executed by the Bidder and the City 6) any addenda 7) any other Solicitation Documents. Also means an Agreement to purchase Goods or Services or both, regardless of whether the agreement is reduced to a single written document.

Electronic Signature means the original signature transmitted and received via electronic transmission of a scanned document, (e.g., PDF or similar format) and are true and valid signatures for all purposes hereunder and shall bind the parties to the same extent as that of an original signature. Any such electronic counterpart shall be of sufficient quality to be legible either electronically or when printed as hardcopy. The City shall determine legibility and acceptability for public record purposes.

Florida Prompt Payment Act means F.S. §§ 255.0705—255.078, as amended from time to time.

Goods means the supplies, materials, commodities, merchandise, food, equipment, or other personal property, excluding real property, that the Bidder will be obligated to provide the City under any resulting

Contract. References to Goods shall mean Commodities.

Local Vendor means a person or business entity which has maintained a permanent place of business with full-time employees within the city limits for a minimum of six months prior to the date Offers were received for the purchase or Contract at issue, which generally provides from such permanent place of business the kinds of Goods or Services solicited, and which at the time of the Solicitation fully complies with state and local laws, including City zoning and licensing ordinances.

Notice of Intent to Award (NOI) means a written notice given by the City stating that staff is recommending award to the listed Proposer. It includes instructions for completing and submitting any Contract that accompanies the NOI.

Offer means Solicitation Submission, Bid, or Proposal, submitted by a Bidder on the prescribed forms setting forth the prices for the work to be performed, and in the case of a Request for Proposals, the credentials, qualifications, and proposed project approach.

Platform means OpenGov, the software currently used by the City. All communications regarding this

Solicitation will be posted at www.codb.us/841/purchasing through the Public Solicitations link. Bidders MUST submit Offers through the Platform. The Platform is utilized by the City and the Bidders to: 1) Allow Bidders to register and manage their company records, 2) Post and issue City Solicitation packages for Bidders from inception to award of a Solicitation, 3) Allow Bidders to submit an Offer Package online, electronically, through the Platform, 4) Allow Bidders to view all public record documents related to an online Solicitation.

Pricing Sheet means the area within the Platform where Bidders will provide their pricing response for the

Solicitation. Also known as Bid Schedule.

Proposal means Solicitation Submission, or Bid, submitted by a Bidder on the prescribed forms setting forth the prices for the work to be performed, and in the case of a Request for Proposals, the credentials, qualifications, and proposed project approach.

Proposer means one who submits a response to a Solicitation; also means Bidder or Respondent

Purchase Order means a written document to an awarded Proposer formalizing the terms and conditions of a proposed transaction.

Respondent one who submits a response to a Solicitation; also means Proposer or Bidder.

Responsible refers to a Proposer that has the necessary skills, ability, capacity, and capability to perform the work required under a Solicitation and is otherwise eligible for award.

Responsive means conforming in all respects to the Solicitation Package, except minor irregularities.

Services means a Proposer's ability to comply with promised delivery dates, specifications, and technical assistance. Also means the furnishing of labor, time, or other form of effort.

Solicitation means the group or collection of information that constitutes detailing the requirements and requesting responses or submittals from eligible Proposers. The information may be in the form of electronic documents, files, and information contained in data fields in the Platform.

Solicitation Deadline means the specific date a time that a Solicitation is due. No Offers will be accepted after this time.

Tabulation Sheet means the opening results of a Solicitation. The Proposer's name, City, and Offer Price will be recorded for Invitations to Bid.

Vendor means Contractor, Consultant, Respondent, Supplier or Proposer to whom the Contract is awarded.

3. SCOPE OF WORK

3.1. 1. Executive Summary

The City of Daytona Beach is commissioning the development of a comprehensive digital platform that integrates a cross-platform mobile application, a web-based administration portal, and a unified Supabase backend. This initiative is designed to enhance civic engagement, streamline access to public information, and modernize the delivery of city services through mobile, web, and emerging immersive technologies.

The scope covers:

• React Native mobile app deployed with Expo EAS, targeting both iOS and Android.

• Web Administration Portal built in Next.js or Nuxt, hosted on Vercel with CI/CD pipelines linked to GitHub.

• Supabase backend for authentication, data storage, file handling, and real-time synchronization.

• AI Assistant (“Ask Daytona”) integrating OpenAI GPT for context-aware responses limited to city-owned data.

• GIS & AR/VR modules leveraging ArcGIS and Agents of Discovery APIs for interactive park and facility experiences.

• Notification System using Resend (email), Twilio (SMS), and Expo Notifications (push) with full subscription management.

This specification defines the technical architecture, security standards, testing requirements, and delivery milestones necessary for a successful deployment. It merges contractual clarity with deep engineering detail to ensure alignment between the City, development contractors, and internal IT staff.

3.2. 2. Ownership & Governance

All intellectual property, source code, databases, designs, and digital assets produced under this contract are the exclusive property of the City of Daytona Beach. No third-party vendor, subcontractor, or developer retains ownership or licensing rights to any portion of the final system.

Account Control

• All environments will be provisioned in City-owned accounts, including but not limited to:

o Apple Developer Program o Google Play Console o Expo.dev (organization workspace) o GitHub (private repositories) o Supabase (project instances & storage buckets) o Vercel (hosting for Admin Portal) o Resend (email delivery) o Twilio (A2P SMS & voice services) o ArcGIS (Esri Developer Account) o Agents of Discovery (Mission API Access) o Microsoft Graph API integration for SharePoint data exchange

Governance Framework

• Project Steering Committee: Comprised of City IT, Communications, and Procurement divisions.

Approves requirements, milestones, and deliverables.

• Change Management: All scope changes must be submitted as formal change requests with impact analysis on budget and timeline.

• Source Control: All repositories reside under the City’s GitHub organization. Pull requests require review and approval from City-designated maintainers.

• Code Ownership: Every line committed to City repos is licensed to the City under permanent exclusive rights. Developers are prohibited from reusing proprietary components outside this project.

• Audit & Access: City administrators retain the right to review logs, deployment pipelines, and cloud configurations at any time.

Deliverable Transfer Protocol

• At project completion, the developer must:

o Transfer ownership of all accounts, tokens, and certificates to the City’s IT department.

o Commit final source code to City-owned repositories with documentation and version tags.

o Deliver a complete asset package (Figma files, source images, icons, fonts, and documentation).

o Provide credential handover and revocation confirmation.

3.3. 3. Project Components

The Daytona Beach Civic Engagement Platform consists of three major components and a set of interconnected subsystems. Together, they form a unified architecture designed for scalability, performance, and maintainability.

3.1 - Mobile Application (React Native + Expo EAS)

The mobile app delivers civic information, city services, and interactive experiences for residents, visitors, and city staff.

• Framework: React Native (Expo SDK 51+), TypeScript-enabled for type safety.

• Distribution: iOS (App Store) and Android (Play Store) via Expo Application Services (EAS).

• Offline-first: Core data cached locally with synchronization on reconnect.

• Authentication: Supabase Auth supporting email/password and optional Microsoft login.

• Data Integration: Real-time Supabase subscriptions and REST endpoints for live updates.

• Modules:

o City Highlights (news, alerts, events) o Events Calendar with RSVP and Add-to-Calendar o Parks & Recreation (with AR/VR experiences) o City Services (directory + quick links) o AI Chat Assistant (“Ask Daytona”) o Dynamic Pages under More tab (fetched from Supabase tables) o Push Notifications (Expo SDK integrated)

Device Compatibility:

• iOS: 14.0 and later (optimized for SE → iPhone 15 Pro Max)

• Android: API 24+ (Nougat and above)

3.2 - Web Administration Portal (Next.js or Nuxt + Vercel)

A responsive, secure content management portal for internal staff.

• Hosting: Vercel under the City’s organizational account.

• Authentication: Supabase Auth with role-based permissions (Admin, Editor, Viewer).

• Primary Functions:

o Manage city highlights, events, and dynamic pages.

o Upload photos, documents, and video content to Supabase Storage.

o Compose and schedule push, SMS, and email notifications.

o Configure external WebView links for the mobile app.

o Manage subscriptions, AI knowledge base, and site settings.

• UI Framework: TailwindCSS + City Design Tokens from Figma.

• CI/CD: Auto-deployment on commit to main via GitHub Actions + Vercel integration.

3.3 - Supabase Backend (Postgres + Edge Functions)

Supabase acts as the unified data backbone.

• Database: PostgreSQL with Row-Level Security (RLS).

• Auth: Email/password, OAuth (optional), JWT-based sessions.

• Storage: Buckets for images, videos, and documents.

• Realtime: WebSocket updates for live event feeds and chat.

• Edge Functions:

o Notification dispatch (Resend, Twilio, Expo) o AI query pre-processing o SharePoint → Supabase sync o Email confirmations and subscription updates o Analytics aggregation for the admin dashboard

• Performance: PostgREST API auto-generated endpoints with caching enabled.

3.4 AI Assistant (“Ask Daytona”)

• Engine: OpenAI GPT-4 (or current stable model).

• Scope: Limited to City of Daytona Beach content only (no open internet access).

• Knowledge Base:

o Data from DaytonaBeach.gov (scraped via controlled crawler).

o City-managed Supabase tables (pages, news, staff directory).

• Functionality:

o Conversational interface with voice input/output.

o Citations to data sources for every response.

o Offline fallback with pre-stored FAQs.

• Privacy: No PII stored in chat history; optional local-only storage per user session.

3.5 Notifications & Communications System

• Email: Resend (transactional + subscription alerts).

• SMS: Twilio (A2P 10DLC registered).

• Push: Expo Notifications.

• Preference Management:

o Users toggle per-channel preferences in the app.

o Stored in Supabase subscriptions and profiles tables.

o Edge Functions handle email verification, STOP/START/HELP compliance, and rate limits.

• Message Templates: Stored in Supabase with variables {first_name}, {event_time}, {cta_link}.

3.6 Third-Party Integrations (WebView Modules)

The mobile app integrates with existing city and partner systems via in-app WebViews. Each link opens inside the app with navigation controls, offline fallback, and share options. Examples:

• SeeClickFix (Report Concerns)

• CivicWeb (Agendas & Minutes)

• Utility Services Portal (Billing)

• Recreation Catalog (Rec1)

• Public Records (JustFOIA)

• Land Management System (IMS16)

• and others listed in Appendix D.

All WebViews inherit the city’s theme colors and include navigation and error handling overlays.

3.4. 4. Data Model & Backend Architecture

Supabase serves as the single source of truth for data flowing between SharePoint, the Admin Portal, and the Mobile App.

All tables enforce Row-Level Security (RLS) and maintain automatic timestamps.

Each service (Resend, Twilio, Expo, OpenAI, ArcGIS) interacts through Edge Functions or authenticated

REST calls.

4.1 Core Schema

Table Purpose Key Fields profiles user identity and contact prefs id uuid pk, email, phone_e164, role, email_verified_at, sms_verified_at posts city highlights / blog entries id uuid, title, excerpt, body_html, category, published_at, author_id events calendar data synced from SharePoint id uuid, title, start_time, end_time, location, category, image_url, rsvp_url pages dynamic pages for “More” tab id, slug, title, status, schedule_at, updated_at content_blocks page elements (text, image, video, form) id, page_id, type, content_json, order_index staff staff directory id, name, title, department_id, email, phone, photo_url departments staff hierarchy id, name, color_hex subscriptions user preferences per list profile_id, list_id, email_enabled, sms_enabled, push_enabled subscription_lists definitions of topics id, key, description, default_email, default_sms, priority notification_events messages queued for dispatch id, list_id, title, body_markdown, scheduled_at notification_dispatches per-user delivery log event_id, profile_id, channel, status, sent_at gis_locations coordinates for parks, buildings id, name, lat, lng, category, amenities kb_documents scraped city content for AI id, url, title, text_content, last_crawled kb_chunks vectorized embeddings for search id, document_id, embedding vector(1536), content, metadata

4.2 Storage Buckets

• public/images → Event & staff photos

• public/videos → DBTV archives & VR assets

• public/documents → PDFs and uploaded forms

• private/user-uploads → Citizen submissions (RLS restricted)

• Each file carries a signed URL with expiry tokens managed through Edge Functions.

4.3 Edge Functions

• /notify/dispatch

Handles queued notifications across email (Resend), SMS (Twilio), and push (Expo). Includes retry logic and idempotency keys.

• /sync/sharepoint Fetches Lists from Microsoft Graph API → normalizes → writes to Supabase tables.

• /ai/search Retrieves embeddings from kb_chunks, performs vector similarity + text filter, returns structured context to OpenAI API.

• /forms/submit Validates and routes incoming forms; uploads attachments to Supabase Storage and sends email confirmation via Resend.

• /analytics/report Aggregates daily events (page views, downloads, notifications sent) for Admin dashboard visualizations.

4.4 Data Flow

A. City Staff Input → SharePoint Lists

B. Automated Sync → Supabase via Graph API

C. Realtime Replication → Mobile App and Admin Portal

D. Edge Functions → Notifications, Search, Forms

E. Cached Offline in SQLite/AsyncStorage

F. User Interaction → Data Updates → Supabase via Auth Session

4.5 Offline and Sync Strategy

• Expo SQLite: Structured caching (events, posts, staff).

• AsyncStorage: Simple key-value (user prefs, theme, session).

• SecureStore: Sensitive tokens (auth, push ID).

• Background Sync: Triggered when network returns; reconciles via timestamp diff.

• Conflict Resolution: “Last write wins” for non-critical data; manual merge for forms.

• Visual Indicator: Offline badge and manual refresh option in UI.

4.6 Performance Targets

• App launch: ≤ 3 s on mid-range device

• API response: ≤ 2 s 95th percentile

• Realtime latency: ≤ 500 ms for event pushes

• Offline cache sync: ≤ 10 s post-reconnect

• Battery impact: ≤ 3 % per hour average use

4.7 Security Implementation

• Row-Level Security on every table with JWT claims.

• Edge Functions authenticated via service role keys.

• All external API calls use server-side proxies to hide credentials.

• Supabase storage signing with 10-minute expiry URLs.

• Logs redact email, phone, address before storage.

4. SPECIAL PROVISIONS

4.1. MINIMUM QUALIFICATIONS

In order to be considered qualified to perform the requested Services, the Bidder must have an active, permanent, and successful operation for a minimum of three years prior to the date of submission of

Bids, and must otherwise have sufficient organizational capacity, equipment, and facilities to provide the requested Services. Formal education and certifications in Computer Science, App development or coding languages will be considered for this project, but they do not guarantee qualification of a bidder for this project. Potential Bidders must also be prepared to exhibit a portfolio of past and current projects with at least a similar scope as this RFP.

4.2. E-VERIFY

E-Verify. - The Proposer (and its subcontractors) have an obligation to utilize the U.S. Department of

Homeland Security’s (DHS) E-Verify system for all newly hired employees. By executing this Contract, the

Proposer certifies that it is registered with, and uses, the E-Verify system for all newly hired employees.

The Contractor must obtain an affidavit from its subcontractors in accordance with paragraph (2)(b) of section 448.095, F.S., and maintain a copy of such affidavit for the duration of the Contract.

This section serves as notice to the Proposer regarding the requirements of section 448.095, F.S., specifically sub-paragraph (2)(c)1, and the City’s obligation to terminate the contract if it has a good faith belief that the Proposer has knowingly violated section 448.09(1), F.S. If terminated for such reason, the

Proposer will not be eligible for award of a public contract for at least one year after the date of such termination. The City reserves the right to order the immediate termination of any contract between the

Proposer and a subcontractor performing work on its behalf should the City develop a good faith belief that the subcontractor has knowingly violated section 448.095(1), F.S.

4.3. RESTRICTIONS, PROHIBITIONS

A. A person or affiliate who has been placed on the Convicted Vendor List following a conviction for a public entity crime may not submit a Proposal to provide any goods or services to a public entity; may not submit a Proposal on a contract with a public entity for the construction or repair of a public building or public work; may not submit a Proposal on leases of real property to a public entity; may not be awarded or perform work as a Contractor, Supplier, subcontractor or Consultant under a contract with any public entity; and may not transact business with any public entity in excess of the threshold amount provided in Section 287.017, Florida Statutes, for

CATEGORY TWO for a period of 36 months from the date of being placed on the Convicted

Vendor List.

B. In accordance with Section 287.134, Florida Statutes, an entity or affiliate who has been placed on the Discriminatory Vendor List, kept by the Florida Department of Management Services, may not submit a Proposal to provide goods or services to a public entity; may not submit Proposal with a public entity for the construction or repair of a public building or public work; may not submit proposals on leases of real property to a public entity; may not be awarded or perform work as a contractor, supplier, subcontractor or consultant under a contract with any public entity; and may not transact business with any public entity.

C. An entity or affiliate who has had its Certificate of Qualification suspended, revoked, denied or have further been determined by the Department to be a non-responsible Contractor may not submit a Proposal or perform work for the construction or repair of a public building or public work on a contract with the Recipient.

D. No funds received pursuant to this Agreement may be expended for lobbying the Florida

Legislature, judicial branch or any state agency.

5. GENERAL CONDITIONS

THIS IS NOT A BID. This is a Request for Proposals issued in accordance with The City of Daytona Beach

Code Chapter 30, Division 3, “Source Selection and Contract Formation”. The Request for Proposal specifies the product(s) or services needed and lists the criteria upon which the Proposals will be evaluated. When received, Proposals will be reviewed and ranked in order, beginning with the one deemed most advantageous to the City. Negotiations will commence with the selected Proposer(s).

Upon completion of satisfactory negotiations, the Contract negotiated as the best will be recommended to the City Commission. A copy of Chapter 30 may be obtained upon request.

5.1. ELECTRONIC PLATFORM

To ensure consideration of your Proposal, please follow these instructions.

The City will only accept online Proposals for this Solicitation through the Platform accessible through

Opengov, the City's online procurement Platform. All solicitations can be accessed through the City’s website: www.codb.us/841/Purchasing under the link to “Public Solicitation”, then by selecting the proper solicitation.

No other forms of online Proposals will be accepted. All Proposals not in compliance with the conditions specified herein are subject to rejection.

Interested Proposers shall contact OpenGov Procurement Support related to any inquiries related to the software. Proposers may contact Support via the blue chat bubble in the bottom right corner of an

OpenGov Procurement webpage or can reach out via email at procurement-support@opengov.com or via phone at (855) 680-4747.

5.2. REQUESTS FOR INTERPRETATIONS

If the Proposer is in doubt as to the meaning of any of the Solicitation Documents or other Exhibits included in this Solicitation, the Proposer may submit a question through the Platform. Such requests must be received by the deadline communicated in the Timeline in the INTRODUCTION in order to be considered. The City is not obligated to respond to such requests.

5.3. ADDENDA TO SOLICITATION DOCUMENTS

Prior to Solicitation opening, the City may, on the City’s own initiative or in response to a request for clarification, furnish Addenda, or answer questions via the Platform for additions or alterations to the https://procurement.opengov.com/portal/codb/projects/221686/document?section=2090360

Solicitation Documents previously supplied by the City. In addition, the City may by Addendum extend the date scheduled for Solicitation opening. The Purchasing representative will make reasonable efforts through the Platform to notify all potential Suppliers of the issuance of an Addendum. The City’s

Purchasing web site address is www.codb.us/841/Purchasing; Addenda may be found under the “Public

Solicitations” link.

Any clarification or interpretation issued by the City in the form of a written Addendum will be deemed to be a part of the Solicitation Documents. No oral clarification or interpretation will be binding. However, the Proposer is solely responsible for ensuring that the Proposal submitted reflects all such

Addenda/Questions and Answers.

5.4. EXECUTION OF OFFER

The City will only accept Offers online through the Platform. No paper Offers will be accepted.

All electronic files uploaded must be in a common format accessible by software programs the City uses. Those common formats are generally described as Microsoft Word (.doc or .docx), Microsoft Excel

(.xls or .xlsx), Microsoft Power Point (.ppt or pptx), or Adobe Portable Document Format (.pdf.). Bidders will not secure, password protect or lock uploaded files; the City must be able to open and view the contents of the file. Bidders will not disable or restrict the ability of the City to print the contents of an uploaded file. Scanned documents or images must be of sufficient quality, no less than 150 dpi, to allow for reading or interpreting the words, drawings, images or sketches. The City may disqualify any Offer that does not meet the criteria stated in this paragraph.

5.5. WITHDRAWAL OF OFFERS

The Proposer may withdraw their submission and resubmit anytime until the specified opening date and time, (i.e., the end of the Offer Phase). Once the Offer Phase has ended the City will be able to view the submissions and begin the evaluation of all Proposals received.

Mere negligence on the part of the Proposer in preparing the Offer does not constitute a right to withdraw the Proposal after opening.

5.6. OPENING DATE

The opening of Proposals will be scheduled at the date and time specified by the Solicitation, or as changed by Addenda or response that the City may issue. At opening, the City will open and record the Proposals so long as they are proper and have been timely submitted. In recording the Proposals, the City will state the name of the Proposer. The Tabulation Sheet will be created on the Platform by the Purchasing representative. The Proposer is solely responsible to ensure that the Proposal is submitted online prior to the end of the Offer Phase. Late Submissions will not be accepted.

5.7. COOPERATIVE PURCHASING

All Proposers awarded Contracts from this Solicitation are required to permit governmental entities to participate in the Contract under the same terms, and conditions except those allowances may be made for differences in delivery costs.

5.8. GENERAL REVIEW PROCEDURES

The Purchasing Code, Chapter 30, Code of the City of Daytona Beach, sets forth the general review procedures for competitive sealed Offers. Under the Purchasing Code, the City Manager is required to evaluate and rank Responsive Proposals in accordance with the criteria identified in the Solicitation.

Before submitting a recommendation for final action on this Solicitation to the City Commission, the City

Manager is authorized to “shortlist’ and negotiate with one or more of the Proposers who submitted the highest ranked Proposals. As part of these negotiations, the City Manager may request revised Offers from shortlisted Proposers.

The City Manager has adopted a policy delegating the task of initially ranking Responsive Offers to a

Selection Committee. The Selection Committee may require personal interviews with Proposers before submitting its recommendations to the City Manager.

5.9. LOCAL PREFERENCE

Pursuant to the Purchasing Code, preferences may be given in the evaluation of Responsive Offers to

Local Vendor. A “Local Vendor” is a Proposer which has maintained a permanent place of business with full-time employees within the city limits of the City of Daytona Beach for a minimum of six months prior to the date Offers were received for the Contract at issue, which generally provides from such permanent place of business the kinds of services solicited, and which at the time of the Solicitation fully complies with state and local laws, including City zoning and licensing ordinances.

In order to qualify as a Local Vendor, the Proposer must submit a properly completed Local Vendor affidavit as part of its Proposal. A Proposer who fails to properly complete and sign this affidavit or submit it with the Proposal will not be considered for local preference in this Solicitation. The City is the ultimate arbiter as to whether the Proposer qualifies as a Local Vendor; and the City may require the

Proposer to submit additional documentation verifying that the Proposer qualifies as a Local Vendor.

A Proposer qualifying as a Local Vendor will be given the following Preferences:

A. At the City’s discretion, the Proposer may be given bonus points of up to 10% of the total available points used to score Offers for ranking purposes. The exact percentage awarded may be adjusted based on the extent of work to be subcontracted to non-local Vendor.

B. After the Selection Committee has evaluated and ranked Offers, if the highest-ranked Local

Proposer’s Proposal would not otherwise be among the list of the highest–ranked Proposals submitted to the City Manager, the list will be modified to include the highest-ranked Local

Vendor’s Proposal. In addition, if the evaluation criteria included price, all of the Proposers on the modified short list will be given the opportunity to submit best and final fee schedules; and final ranking provided by the Selection Committee will be based on the best and final Offers. For purposes herein, the reference to “best and final” will not serve to alter the City Manager’s authority from requiring a short listed Proposer to submit a revised Offer.

Note: If this Request for Proposals will use Federal Funding, this section will not apply.

5.10. MINORITY AND WOMEN WORK FORCE PARTICIPATION

The City has an established policy of 1) promoting Minority and Women-Owned Business Enterprise participation in business contracts and 2) requiring Proposers doing business with the City to use good faith efforts to promote cultural diversity and minority participation in the work force, including managerial positions. Proposers must provide information as part of the Proposal acknowledging its understanding and willingness to comply with the Purchasing Code of The City of Daytona Beach.

5.11. REJECTION OF OFFERS

The City reserves the right to reject any or all Proposals in whole or in part and to award by items, parts of items, or by any aggregate group of items specified. The City also reserves the right to waive technical defect when in its judgment the best interests of the City thereby will be served.

5.12. AWARD

The award will be made by the City to the Proposer most qualified and offering the best value to the City, which will be determined by evaluation of Proposals using the evaluation criteria contained in the

Solicitation, and in accordance with applicable rules and regulations governing the purchase and Contract adopted and established by the City, and the State of Florida.

Any Contract resulting from this Solicitation may, in the alternative, be awarded by the City of Daytona

Beach Community Redevelopment Agency (CRA). Therefore, any Offers submitted in response to this

Solicitation shall be deemed to be Offers to the CRA as well as the City. Any final written contract may be with the CRA instead of the City, and in such instances, any required insurance, performance and payment bonds, may be required to run in favor of the CRA in addition to or in lieu of the City.

5.13. SELECTION PROCESS

For the purpose of selecting the most qualified Proposal, the City will use a competitive selection process as set forth in pertinent City and State procurement requirements. The procedure will involve the following steps:

A. The City will advertise and email notice of formal Requests for Proposals to interested

Proposers. The City’s Selection Committee will review, rank, and shortlist all Proposals received by the established deadline for submission. Oral presentations by the short-listed Proposers to clarify their Offers may be required. These presentations will serve to explain implementation techniques integral to the written Proposal. Subsequent to the receipt of Proposals, the City may schedule a time for each requested oral presentation at a place convenient to the City.

B. The City’s Selection Committee will then rank each Proposal and prepare a recommendation for approval by the City Manager. Upon receipt of the City Manager’s approval, the City’s Project

Manager shall negotiate a contract with the highest ranked Proposer(s) approved by the City

Manager. Should the Project Manager be unable to negotiate a satisfactory contract with the any of the shortlisted Proposers, the City Manager, or designee, shall terminate such negotiations with any or all of the shortlisted Proposers and begin negotiations with remaining

Proposers based on ranking, until negotiations are successful or this Solicitation is cancelled.

C. The City Commission has the sole authority to bind the City to the terms and conditions of a contract that has been approved in a public meeting of the City Commission. The City

Commission reserves the right to modify or reject any contract for the acquisition of goods and/or services submitted to it for consideration.

5.14. LICENSES, PERMITS, AND FEES

All Proposals submitted shall include in the price the cost of any business or professional licenses, permits or fees required by the City and any agency having jurisdiction over the Services solicited through this Request for Proposal.

5.15. PATENT INFRINGEMENT

By submission of a Proposal, the Proposer certifies that the Services to be furnished will not infringe any valid patent, copyright, or trademark and the successful Proposer shall, at his/her own expense, defend any and all actions or suits charging such infringement and hold the City harmless in case of any such infringements.

5.16. TAXES

All Proposals shall be exclusive of federal taxes. Tax exemption certificates will be furnished upon request.

5.17. FLORIDA PUBLIC RECORDS LAW

Sealed Offers received by the City pursuant to the Request for Proposals will be temporarily exempt from disclosure in accordance with Florida’s Public Records Laws. F.S. §119, states that Offers are not public record for 30 days from the date of the opening of the Offers or the date a Notice of Intent to

Award is posted, whichever is first. Thereafter, all Offers will be open for a personal inspection by any person pursuant to Public Records Law.

If the Proposer believes that the Offer or any portion thereof is permanently exempt from disclosure under the public records laws, the Proposer must state the grounds for this position in CAPITAL LETTERS in a certified letter addressed to the Purchasing Agent and received at least 3 days prior to the Offer opening. The Proposer will be contacted prior to the opening of the Offer and a determination will be made as to whether or not it is exempt prior to opening. If a determination is made that it is not exempt from disclosure, the Proposer may in writing request the return of the sealed Proposal.

5.18. QUALIFYING PROPOSERS

Prior to awarding of Offer, the City may require submission by Proposer of complete financial statement and questionnaire describing Proposer’s financial ability and experience in performance of similar work.

5.19. RULES AND REGULATIONS

All work performed under this agreement shall be in strict compliance with local, State and Federal laws, rules and regulations. Proposer shall assume all liability for fines and penalties assessed by the authorities for any infractions.

5.20. NO COSTS

The City of Daytona Beach bears no responsibility for any costs incurred in the preparation of the

Proposal.

5.21. INTERNET/WEB SERVICES

For the purposes of this paragraph, any Services or products offered to the public via the internet or online must comply with WCAG 2.0 AA in order to be deemed ADA compliant. The City will provide

Contractor with prompt written notice with respect to any ADA deficiencies of which the City is aware and Contractor will promptly correct such deficiencies. If the County, the Department of Justice, or other governmental entity tasked with the enforcement of the ADA ("Enforcement Agency") notes any deficiency in the facilities, practices, services, or operations of the Contractor furnished or provided in connection with this Agreement, Contractor shall, at no additional charge or cost to the City, immediately cure any such deficiencies without delay to the satisfaction of such Enforcement Agency.

Contractor further agrees that it shall, to the extent permitted by law, indemnify, defend, and hold harmless the City against any and all claims, sanctions, or penalties assessed against the City, which claims, sanctions, or penalties arise or otherwise result from the Contractor's failure to comply with the

ADA or WCAG 2.0 AA, for online or internet services or products.

5.22. FEDERAL CONTRACT PROVISIONS

This is an acknowledgment that FEMA financial assistance may be used to fund the agreement. The Contractor will comply with all applicable federal laws, regulations, and Executive Orders, including FEMA policies, procedures, and directives. The Contractor shall comply with all uniform administrative requirements, cost principles, and audit requirements for federal awards. Contractor shall ensure that all subcontracts comply with all applicable federal laws, regulations, and Executive Orders, including FEMA policies, procedures, and directives.

A. Equal Employment Opportunity. For all contracts for construction work which is defined as the construction, rehabilitation, alteration, conversion, extension, demolition or repair of buildings, highways, or other changes or improvements to real property, including facilities providing utility services. The term also includes the supervision, inspection, and other onsite functions incidental to the actual construction.

This requirement applies to all FEMA grant and cooperative agreement programs.

During the performance of this contract, the contractor agrees as follows:

(1) The contractor will not discriminate against any employee or applicant for employment because of race, color, religion, sex, sexual orientation, gender identity, or national origin. The contractor will take affirmative action to ensure that applicants are employed, and that employees are treated during employment without regard to their race, color, religion, sex, sexual orientation, gender identity, or national origin. Such action shall include, but not be limited to the following:

Employment, upgrading, demotion, or transfer; recruitment or recruitment advertising; layoff or termination;

rates of pay or other forms of compensation; and selection for training, including apprenticeship. The contractor agrees to post in conspicuous places, available to employees and applicants for employment, notices to be provided setting forth the provisions of this nondiscrimination clause.

(2) The contractor will, in all solicitations or advertisements for employees placed by or on behalf of the contractor, state that all qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, or national origin.

(3) The contractor will not discharge or in any other manner discriminate against any employee or applicant for employment because such employee or applicant has inquired about, discussed, or disclosed the compensation of the employee or applicant or another employee or applicant. This provision shall not apply to instances in which an employee who has access to the compensation information of other employees or applicants as a part of such employee's essential job functions discloses the compensation of such other employees or applicants to individuals who do not otherwise have access to such information, unless such disclosure is in response to a formal complaint or charge, in furtherance of an investigation, proceeding, hearing, or action, including an investigation conducted by the employer, or is consistent with the contractor's legal duty to furnish information.

(4) The contractor will send to each labor union or representative of workers with which he has a collective bargaining agreement or other contract or understanding, a notice to be provided advising the said labor union or workers' representatives of the contractor's commitments under this section and shall post copies of the notice in conspicuous places available to employees and applicants for employment.

(5) The contractor will comply with all provisions of Executive Order 11246 of September 24, 1965, and of the rules, regulations, and relevant orders of the Secretary of Labor.

(6) The contractor will furnish all information and reports required by Executive Order 11246 of

September 24, 1965, and by rules, regulations, and orders of the Secretary of Labor, or pursuant thereto, and will permit access to his books, records, and accounts by the administering agency and the Secretary of Labor for purposes of investigation to ascertain compliance with such rules, regulations, and orders.

(7) In the event of the contractor's noncompliance with the nondiscrimination clauses of this contract or with any of the said rules, regulations, or orders, this contract may be canceled, terminated, or suspended in whole or in part and the contractor may be declared ineligible for further Government contracts or federally assisted construction contracts in accordance with procedures authorized in Executive Order 11246 of

September 24, 1965, and such other sanctions may be imposed and remedies invoked as provided in Executive

Order 11246 of September 24, 1965, or by rule, regulation, or order of the Secretary of Labor, or as otherwise provided by law.

(8) The contractor will include the portion of the sentence immediately preceding paragraph (1) and the provisions of paragraphs (1) through (8) in every subcontract or purchase order unless exempted by rules, regulations, or orders of the Secretary of Labor issued pursuant to section 204 of Executive Order 11246 of

September 24, 1965, so that such provisions will be binding upon each subcontractor or vendor. The contractor will take such action with respect to any subcontract or purchase order as the administering agency may direct as a means of enforcing such provisions, including sanctions for noncompliance:

Provided, however, that in the event a contractor becomes involved in, or is threatened with, litigation with a subcontractor or vendor as a result of such direction by the administering agency, the contractor may request the United States to enter into such litigation to protect the interests of the United States.

The applicant further agrees that it will be bound by the above equal opportunity clause with respect to its own employment practices when it participates in federally assisted construction work: Provided, That if the applicant so participating is a State or local government, the above equal opportunity clause is not applicable to any agency, instrumentality or subdivision of such government which does not participate in work on or under the contract.

The applicant agrees that it will assist and cooperate actively with the administering agency and the Secretary of Labor in obtaining the compliance of contractors and subcontractors with the equal opportunity clause and the rules, regulations, and relevant orders of the Secretary of Labor, that it will furnish the administering agency and the Secretary of Labor such information as they may require for the supervision of such compliance, and that it will otherwise assist the administering agency in the discharge of the agency's primary responsibility for securing compliance.

The applicant further agrees that it will refrain from entering into any contract or contract modification subject to Executive Order 11246 of September 24, 1965, with a contractor debarred from, or who has not demonstrated eligibility for, Government contracts and federally assisted construction contracts pursuant to the Executive Order and will carry out such sanctions and penalties for violation of the equal opportunity clause as may be imposed upon contractors and subcontractors by the administering agency or the Secretary of Labor pursuant to Part II, Subpart D of the Executive Order. In addition, the applicant agrees that if it fails or refuses to comply with these undertakings, the administering agency may take any or all of the following actions:

Cancel, terminate, or suspend in whole or in part this grant (contract, loan, insurance, guarantee); refrain from extending any further assistance to the applicant under the program with respect to which the failure or refund occurred until satisfactory assurance of future compliance has been received from such applicant; and refer the case to the Department of Justice for appropriate legal proceedings.

B. Contract Work Hours and Safety Standards Act. This requirement applies to all FEMA contracts awarded by the non- federal entity in excess of $100,000 under grant and cooperative agreement programs that involve the employment of mechanics or laborers. It is applicable to construction work. These requirements do not apply to the purchase of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.

Compliance with the Contract Work Hours and Safety Standards Act.

Overtime requirements. No contractor or subcontractor contracting for any part of the contract work which may require or involve the employment of laborers or mechanics shall require or permit any such laborer or mechanic in any workweek in which he or she is employed on such work to work in excess of forty hours in such workweek unless such laborer or mechanic receives compensation at a rate not less than one and one-half times the basic rate of pay for all hours worked in excess of forty hours in such workweek.

Violation; liability for unpaid wages; liquidated damages. In the event of any violation of the clause set forth in paragraph (b)(1) of this section the contractor and any subcontractor responsible therefor shall be liable for the unpaid wages. In addition, such contractor and subcontractor shall be liable to the United States (in the case of work done under contract for the District of Columbia or a territory, to such District or to such territory), for liquidated damages. Such liquidated damages shall be computed with respect to each individual laborer or mechanic, including watchmen and guards, employed in violation of the clause set forth in paragraph (b)(1) of this section, in the sum of $27 for each calendar day on which such individual was required or permitted to work in excess of the standard workweek of forty hours without payment of the overtime wages required by the clause set forth in paragraph (b)(1) of this section.

Withholding for unpaid wages and liquidated damages. The City of Daytona Beach or State of Florida shall upon its own action or upon written request of an authorized representative of the Department of Labor…