Invitation to Negotiate

EXHIBIT A – SCOPE OF SERVICES

LOI # : C007036

TITLE: Advanced Metering Infrastructure Program

1. SCOPE OF SERVICES OVERVIEW

1.1 The Central Florida Tourism Oversight District (CFTOD) is seeking qualified vendors to implement a comprehensive Advanced Metering Infrastructure (AMI) solution. This project includes the deployment of a multi-utility AMI system, replacement of all the existing meters, the migration of legacy data from FoxPro to a modern SQL database, and the establishment of robust data retention and ownership protocols. The objective is to modernize metering, enhance operational efficiency, and ensure secure, scalable, and compliant data management throughout the organization.

1.2 All meters must be new. Reuse of existing meters or communications modules is not permitted.

2. BACKGROUND

2.1 The Central Florida Tourism Oversight District (the CFTOD or, the District) is a unique entity comprised of seven utilities including natural gas, potable water, reclaimed water, wastewater, electric, hot water and chilled water that provide utility services to area customers. The District is requesting submittals from qualified advanced metering infrastructure (AMI) vendors able to deliver a comprehensive solution including meters, endpoints, network and headend system to the District’s seven utilities.

2.2 This project will be implemented in multi-year stages, with each stage providing metering and infrastructure to a different District utility or utilities. The first stage of this project will provide metering and infrastructure for the natural gas utility. The following Scope of Services outlines the natural gas utility needs. It also outlines the needs and requirements for the other utilities. All proposers should be able to provide AMI services that are inclusive of all the District utilities noted above. The proposer should include infrastructure and implementation for all the utilities in their proposal and pricing.

3. SCOPE OF SERVICES

3.1 In the first phase of work, the vendor will be required to implement and install an AMI system (including meters, network, and data systems) for the natural gas utility. Once this phase is underway, the other utilities will be gradually incorporated into the program. The proposer should provide a solution for system-wide AMI that incorporates the information and requirements herein and would best suit the needs of the District’s seven utilities. The rollout of this AMI solution should be complete by the end of 2027 (full AMI across all utilities).

3.2 A complete proposal will include the following topics:

A. Proposed approach to update all metering systems through AMI, including schedule;

B. Technical specifications for proposed meters, endpoints and network including:

1. Useful operating life and battery life of endpoints;

2. Maintenance and testing needs for all proposed meters and endpoints;

3. Network equipment;

4. Endpoint events and alarms;

C. Headend system specifications & operations;

D. Software systems and integrations including:

1. Configurability and firmware management;

E. IT standards and security including:

1. Cyber security and backhaul;

F. Testing and system acceptance;

G. Warranty including:

1. All equipment and network devices;

2. Maintenance requirements;

H. Installation support services including:

1. Natural Gas; and

2. Water (potable, reclaimed, hot and chilled).

Note: Installation is not required for the Electric Utility as this will be self-performed.

3.3 Metering Systems Information

A. The proposer is required to provide an AMI system that will be compatible with all the District’s utilities (natural gas, potable and reclaimed water, electric and hot and chilled water). This system shall include only new meters. They must all be integrated to a single Customer Information System

(CIS).

B. The following details describing the current infrastructure of District utilities are for information and are to be used to construct and price this proposal. All meter and endpoint totals are approximate and should be verified upon award by the proposer for any “Best and Final” offer as part of the negotiation process.

C. The natural gas utility will be the first to fully implement this AMI program. Currently, the majority of the utility’s existing meters are manually read. For natural gas, The District shall replace all existing meters. An estimated 222 meters will be replaced, and 222 endpoints will be installed on the new meters.

Natural Gas Utility Infrastructure Count

Meters to be Supplied 222

New Endpoints to be Supplied 222

D. The water utility (including both potable and reclaimed systems) currently utilizes Sensus endpoints to read the majority of meters (approximately 435) with a handheld receiver while driving the property. The remaining water meters (approximately 97) are read manually. All existing water meters, including those currently equipped with Sensus endpoints and those read manually, shall be replaced with new meters and fitted with new endpoints as part of this project.

Water Utility Infrastructure Count

Meters to be Supplied 532

New Endpoints to be Supplied 532

E. The electric utility currently has an Itron AMI system in place with approximately 1,100 existing meters utilizing this network. Approximately 400 meters are currently read via Itron AMR, and around 25 meters are read manually. All existing electric meters, including AMI, AMR, and manually read units, shall be replaced under this program and fitted with new endpoints.

Note that only infrastructure is necessary in the proposal for the Electric Utility, with all installation to be self-performed.

Electric Utility Infrastructure Count

Meters to be Replaced 1605

New Endpoints to be Supplied 1605

F. The hot and chilled water utility has a combination of Aquisuite AMI and manual reading of its existing meters (approximately 40). Each of these meters will need to be replaced with a new meter and fitted with an endpoint as part of this program.

Hot and Chilled Water Utility Infrastructure Count

Meters to be Replaced 40

New Endpoints to be Supplied 40

4. GENERAL AMI SYSTEM REQUIREMENTS

4.1 Meter Specifications:

A. General Specifications:

1. Digital, pulse, or encoder outputs suitable for wired or non-RF communications

2. Support for interval data collection

3. Tamper and diagnostic event reporting

4. Manufacturer warranty (minimum length as defined by utility requirements)

5. Accuracy warranty (10–20 years depending on commodity)

6. Parts and labor coverage for defects; optional extended coverage available

Electric meters will be installed by utility staff. Replacement of water, gas, thermal, and reclaimed water meters will be performed by the vendor or contracted personnel.

B. Communication Architecture

1. Local / Neighborhood Network (Meter-to-Collector Communications)

i. The proposed AMI solution shall utilize RF communications exclusively for the local meter network, including meter-to-meter, meter-to-collector, and collector-to-collector mesh operations.

ii. RF technologies deployed for the local mesh network must support self-healing, self-configuring operation and maintain reliable bidirectional communication between endpoints.

iii. The vendor shall describe:

a. RF frequency bands used

b. Mesh topology (routing, redundancy, latency expectations)

c. Typical range and density assumptions

d. Interference mitigation strategies

iv. RF communication must comply with all applicable FCC requirements and local radio regulations.

2. Backhaul Communications (Field Network to Head-End)

i. The AMI backhaul shall not rely on RF communications except in documented exceptional cases.

ii. Non-RF technologies are required and shall be preferred for all backhaul communication between network nodes, data concentrators, and the AMI head-end system. Accepted non-RF technologies include, but are not limited to:

a. Fiber optic

b. Ethernet/IP (public or private network)

c. Cellular (LTE, LTE-M, NB-IoT, or equivalent)

d. Licensed microwave or point-to-point non-RF terrestrial links

e. DSL, cable, or other IP-based broadband infrastructure

iii. The proposer shall identify and justify the selected non-RF backhaul technology and demonstrate:

a. End-to-end network reliability

b. Latency and throughput performance

c. Security and encryption measures

d. Scalability to support future meter deployment

3. Preference and Evaluation Scoring

i. Proposals using non-RF backhaul technologies will receive higher technical evaluation scores than proposals using RF or unlicensed spectrum for backhaul.

ii. Use of RF communications for backhaul will only be considered where the vendor can document no feasible non-RF alternative exists, and where RF backhaul performance meets all RFP technical, security, and reliability requirements.

4. Security Requirements

i. All communications, both RF and non-RF, must support industry-standard encryption (AES-256 or higher) and mutual authentication.

ii. The vendor shall provide documentation describing network segmentation between:

a. Local mesh (RF domain)

b. Backhaul transport network

c. Head-end system

iii. Any RF components must incorporate protection against:

a. Packet injection

b. Replay attacks

c. Unauthorized endpoint association

5. Performance Requirements

i. The proposed system must support:

a. Minimum 99.5% daily meter read success rate

b. Round-trip latency suitable for remote disconnect/reconnect operation

c. Time-synchronized data collection and event reporting

ii. Backhaul links must ensure bandwidth sufficient for real-time monitoring, firmware upgrades, and event alarms.

6. Documentation and Network Design Deliverables

i. The proposal must include:

a. Communications architecture diagram showing RF local mesh and non-RF backhaul separation

b. Network capacity planning and redundancy considerations

c. Cybersecurity design for layered communication domains

d. Field device specifications, including radios, collectors, and backhaul interfaces

4.2 Communication Technologies

A. Highly preferred: Non-RF communications (fiber, Ethernet/IP, broadband over power line, wired PLC, municipal infrastructure) for communication to head-end systems. Meters may use RF technology

B. RF technologies only if wired alternatives are not viable, and only with explicit justification

C. Network must comply with utility cybersecurity standards, including encryption, multi-factor access, and continuous monitoring

D. All communications must ensure secure data transmission and meet regulatory requirements

4.3 Cloud Architecture

A. All meter and system data to reside in a secure, cloud-based environment B. Automatic elastic scaling, geographic redundancy, and ≥99.9% uptime C. Compliance with NIST cybersecurity standards and applicable regulations D. Support for utility data retention policies E. The AMI architecture must include a customer web portal for displaying consumption, alerts, and account information.

4.4 Head-End System (HES) and Meter Data Management (MDM)

A. Cloud-hosted HES for collecting, validating, and encrypting interval meter data B. MDM must be multi-commodity capable and support validation, estimation, and editing (VEE) C. Integration with customer information system (CIS), portal, and analytics tools D. Support for net and totalized metering (customer and location levels) E. Interval data down to 5 minutes (electric) and 15–60 minutes (other utilities) F. Both net, totalized, and deduct metering must be available for billing and analytics.

4.5 Customer Portal

A. Cloud-hosted, mobile-responsive B. Displays near real-time or daily consumption, billing history, alerts, and usage analytics C. Integrated login with CIS (SSO or shared identity) D. Optional: Budget alerts, trend forecasting, text/email notifications

4.6 Installation, Deployment, and Field Work

A. Vendor/contractor to provide all staff for non-electric meter replacements B. Scheduling to minimize customer impact; notifications and off-peak work as needed C. Uniformed, badged staff; GPS time-stamped and photo-documented installations D. All endpoint activations must be recorded in the utility’s asset management system

4.7 Warranty, Maintenance, and Support

A. Meter warranties (accuracy, parts, labor); optional 5–10 year extensions B. Cloud software SLAs (≥99.9% uptime), 24/7 technical support, cybersecurity and firmware updates C. Long-term maintenance: meter health analytics, lifecycle tracking, replacement thresholds

4.8 Optional Enhancements

A. Outage management integration (electric) B. Pressure/temperature sensor integration (water, gas) C. Demand response or load control features D. Advanced analytics dashboards (leak detection, load forecasting, thermal efficiency)

5. Database Upgrade and Integration

5.1 FoxPro System Assessment

A. Current system uses FoxPro for operational and customer records B. Challenges: scalability, security, real-time data exchange

5.2 SQL Migration Plan

A. Preserve all data fields and relationships during migration B. Adopt a modern SQL platform (e.g., Microsoft SQL Server, PostgreSQL) C. Implement high-availability, disaster recovery, and encryption (at rest and in transit) D. Use ETL tools and custom scripts for data transformation and normalization E. Conduct pre- and post-migration validation (profiling, record counts, integrity checks) F. Retain FoxPro archives for audit and rollback

5.3 Integration with AMI System

A. Develop standardized APIs or middleware for seamless interoperability B. Automated data synchronization and error handling C. Real-time data exchange with AMI for operational and customer records D. Testing: data integrity, functional, load, and user acceptance testing

5.4 Training and Support

A. User training: role-specific documentation, hands-on workshops, Q&A sessions B. System documentation, FAQs, ongoing support channels

5.5 Project Timeline and Milestones

The vendor must submit the milestone schedule and project timeline using the Project Timeline and Milestones (EXHIBIT C). Assume contract awarded August 2026.

Project Phases:

A. Assessment & Planning: System evaluation and requirements review.

B. Data Mapping & Design: Schema design and preparation of mapping documentation.

C. Migration Development: Development of ETL tools and execution of test migrations.

D. Integration Setup: AMI connectivity established and tested.

E. Testing & Validation: Completion of data and system testing.

F. Training & Go-Live: User training, documentation delivery, and production rollout.

6. DATA RETENTION AND OWNERSHIP

6.1 Legacy Data Integration

The vendor is responsible for the secure migration of all legacy data into the new AMI platform.

Historical data must be accessible and managed in line with CFTOD policies, ensuring continuity and compliance.

6.2 Data Ownership Terms

A. All data generated, collected, transmitted, or stored by the AMI system is the exclusive property of

CFTOD.

B. The vendor and subcontractors have no ownership rights to AMI data.

C. CFTOD reserves all rights to access, use, copy, transfer, and manage AMI data.

D. Vendor may only access or use data as explicitly authorized in writing to fulfill contractual obligations.

E. No sharing, selling, or distribution of AMI data to third parties without CFTOD’s written consent.

6.3 Data Retention Policies

A. Data must be retained securely for the contract duration and any additional period required by

CFTOD or law.

B. Upon contract expiration or termination, all data (including backups and archives) must be returned to CFTOD in an agreed format and all vendor copies deleted, unless required by law.

C. Vendor must provide written confirmation of deletion.

6.4 Security and Compliance

A. Vendor must implement robust technical and organizational measures to protect all AMI data from unauthorized access, disclosure, alteration, or destruction.

B. Immediate notification to CFTOD in the event of any data breach or suspected compromise.

C. Compliance with all applicable data privacy, protection, and retention laws and regulations.

D. Documented data handling practices, subject to CFTOD audit.