2026-02-UT - Cellular AMI Natural Gas Solution

INVITATION TO BID

2026-02-UT

CELLULAR AMI NATURAL GAS SOLUTION

The City of DeFuniak Springs will be accepting sealed bids for the purchase of a cellular AMI natural gas solution and associated meters/registers.

Bids will be accepted at City Hall located at 1350 Baldwin Ave, P.O. Box 685, DeFuniak Springs, FL 32433 until 2:00 p.m. CT Tuesday June 9, 2026. Bids will be opened on Tuesday June 9, 2026, at 2:01 p.m. at City Hall in the Council Chambers located at 1350 Baldwin Ave. Bids shall be clearly marked on the outside of the envelope, "City Clerk: ITB 2026-02-UT Cellular AMI Natural Gas Solution." Any bids received after 2:00 p.m. CT on the above date will not be accepted and will be returned unopened to the bidder.

You can obtain a copy of the specifications at https://www.defuniaksprings.net, City Hall, 1350 Baldwin Avenue, DeFuniak Springs, Florida 32433, or by calling Madison Lewis, City Clerk, at 850-892-8500 Ext. 1103.

The City of DeFuniak Springs reserves the right to reject any and all bids, waive any formalities, and award in the best interest of the City of DeFuniak Springs. The City of DeFuniak Springs is an Equal Opportunity/Affirmative Action/ADS Employer and a Drug Free Workplace.

PROJECT SCOPE

Direct integration and transfer from the city's existing meter reading and billing system software to a new proposed system. Provide in-depth training to all responsible city staff and assist with the successful completion of account transfer and setup including but not limited to customer account or portal set up. The City of DeFuniak Springs has an estimated 6 different types of natural gas meters ranging from American, Rockwell, Roots, Equigas, Invensys, and Metris within the system. In total, the City has approximately 1,000 residential customers and 240 commercial customers. As part of this bid, the City is also seeking the following services: project management, training, back-office system integration, management of endpoint deployments, and AMI managed services.

PROSPECTIVE BIDDER INSTRUCTIONS

City Contact

If you require clarification or have questions about this request, please contact the following. We will share all submitted questions and their responses with all participating bidders.

Name: Madison Lewis Title: City Clerk Phone: (850) 892-8500 Email: cityclerk@defuniaksprings.net

Questions Regarding Bid Requirements

Please address questions regarding this ITB package to: Madison Lewis, City Clerk

All questions shall be submitted no later than: May 21, 2026

Questions received after this date will not be considered.

Bid Schedule of Events

Bid Issuance April 29, 2026

Questions Due May 21, 2026

Bids DUE June 9, 2026

Recommendation to Award to the City Council June 22, 2026

Submission Instructions

Bids will be accepted at City Hall located at 1350 Baldwin Ave, P.O. Box 685, DeFuniak Springs, FL 32433 until 2:00 p.m. CT Tuesday June 9, 2026. Bids will be opened on Tuesday June 9, 2026, at 2:01 p.m. at City Hall in the Council Chambers located at 1350 Baldwin Ave.

Proposals must be submitted with one (1) unbound original and one (1) electronic copy (PDF Format) in a sealed envelope clearly marked with the name of the firm, "City Clerk: ITB 2026-02-UT Cellular AMI Natural Gas Solution." Proposals not including the outlined information may be deemed non-responsive and excluded from consideration.

BID PACKAGE REQUIREMENTS

Cover Letter

The Bidder is to provide the full contact information (name, title, email, and phone number) for their primary representative for this ITB. City of DeFuniak Springs will direct all questions regarding Bidder's proposal to this contact. Also identify any third parties or business partners that will be involved in this project and their proposed relationship with Bidder and City of DeFuniak Springs.

Executive Summary

The Bidder is to provide a summary of their proposed solution and how it will meet City of DeFuniak Springs's overall business and project objectives. Please summarize those benefits that other utilities with similar objectives have experienced with the proposed solution. Also include a summary of Bidder's competitive solution differentiators.

Technical Proposal

Bidder is to include the following sections in their Technical Proposal:

Solution Summary

The Bidder is to summarize the solution and its key components and services. Be clear and concise. Note important technical and performance attributes, functional features, and operational benefits.

Component Description

The Technical Proposal must include descriptions of the proposed components of the solution including meters, network communication modules, field area network devices [if applicable], and software management system.

Network Design

Bidder is to describe their network design process and to include quantities for specific network equipment required to cover the service area.

Services Proposal

Bidder, describe your deployment methodology and approach to City of DeFuniak Springs's project. Specifically, describe the following:

Bidder project team roles and responsibilities

City of DeFuniak Springs project team roles and responsibilities

Services provided by Bidder

Training provided by Bidder

Additional services/training available to the City at additional cost.

Solution Hosting

The Bidder must host the solution's software via a proposed Software-as-a-Service (SaaS) model. The Bidder is to provide details of the cloud environment, security, maintenance, technical support, and service levels included in their SaaS offering.

Compliance with Technical Questions

The Bidder is to provide a brief response to each of the items listed in the Compliance to Technical Requirements section. We recommend that you save a copy of this proposal's Compliance to Technical Requirements section and include your responses within that document.

Responding to Technical Questions

The Bidder is to provide a detailed response to each of the items listed in the Technical Questions section. You may include your responses to these questions in a separate document. Please include product images, screenshots, reference tables, or other information, as applicable, to support each response.

Commercial Proposal

System Pricing

The Bidder's pricing must provide the City of DeFuniak Springs's cost for the solution described in the Bidders' technical proposal. This base system offer must meet the requirements provided in the ITB's Technical Requirements section.

Hardware costs must be complete and include all equipment (i.e. cables, mounting kits, etc.) required for the installation and programming of equipment in the field or meter shop. Standard hardware warranties must be clearly identified in the pricing proposal.

Additional or optional pricing should be clearly labeled as Optional, and Bidders should provide a description of the option's benefit to City of DeFuniak Springs.

Software Subscription Fee

Annual software fees must be complete and include the following:

Annual software license and maintenance fees for Bidder's SaaS solution (software management system, any required third-party software, such as database and operating system software, and backhaul costs).

All fees associated with upgrading the Bidder's SaaS solution.

99.5% availability of Bidder's SaaS solution.

All pricing must be provided in US dollars and remain valid for 90 days following the ITB submission date listed in Instruction to Bidders, above.

Meter/Registers

918 residential meters

187 commercial meters

Majority of city meters are American meters with radios being side mount for residentials and commercials being top mount.

Terms and Conditions

The Bidder must provide sample agreements of standard terms and conditions for the purchase and delivery of the proposed solution.

Bidder Information

The Bidder must include the following general information:

Corporate profile

Annual report or financial records for the previous three (3) fiscal years

Sample agreements that include the Bidder's standard terms and conditions for the purchase and delivery of the proposed solution.

References

Please provide a list of customers (including numbers of meters) currently using the proposed solution. Also provide three recent (3) project references that meet the following criteria: .

They must have a similar solution configuration, in terms of software management system, device types, network endpoint counts, etc.

They must include utility contact information for a person who worked closely with the project implantation and deployment.

They must have been delivered within the past 5 years.

COMPLIANCE TO TECHNICAL REQUIREMENTS

Compliance Response Instructions

City of DeFuniak Springs wants to understand your AMI solution, its capabilities, and your proposed offer. The following technical requirements are designed to help City of DeFuniak Springs assess and compare AMI systems.

For each requirement, please provide a concise response, as described in the following table, that indicates your compliance with each requirement. We recommend that you save a copy of this proposal's Compliance to Technical Requirements section and include your responses within that document.

Cellular Gas Communication Modules

Third-Party Compatibility

The gas module must be capable of interfacing with and reading gas meters from most major meter manufacturers.

The gas modules must support residential and commercial direct mount, diaphragm, and rotary models, as well as electronic volume correctors.

Data Collection

The gas modules must record consumption with 99.999% accuracy between the index read and the module read.

The gas module must be configurable to collect hourly or sub-hourly interval readings for all customers.

The gas module must have storage capacity for 160 days of hourly interval data.

The gas module must be capable of detecting and transmitting event and alarm data.

The gas module must support reporting event and alarm conditions for:

Tilt Tamper (Direct mount modules)

Magnetic Tamper (Direct mount modules)

Cut Cable (Remote mount modules)

High Flow

Low Battery

Communications

The gas module must support both cellular and RF communications to support both cellular AMI network and mobile "drive-by" use cases.

The gas module must support cellular LWPA LTE-M Cat-M1, NB-IoT Cat-NB1, and 5G-ready communication networks.

The gas module must be capable of two-way communication with the AMI system for the purposes of data collection, time synchronization, firmware, and software updates.

The gas module must transmit data to the software management system at least twice daily.

The gas module must be capable of transmitting on-demand readings when requested from the software management system.

For security, the gas module must support data authentication and AES-256 encryption.

The gas module must support remote configuration changes.

The gas module must support remote firmware update downloads.

Other

The gas module must have a UL Class I Division 1 rating.

The gas module must have a 20-year service life for electronics and battery.

Cellular Backhaul Communications

The AMI network must have a cellular backhaul.

The solution must support multiple cellular carriers.

The solution provider must manage the cellular connectivity relationship(s) on behalf of the utility.

Software Management System

User Interface

A top priority is that the solution's software management system user interface be straightforward, intuitive, easy to use, and quick to learn. Please attach supplemental materials that show the user interface and highlight its key system management features.

The AMI software management system must provide network management and monitoring for all field area network devices through a single graphical user interface.

The AMI software management system must provide a graphical user interface to monitor the status of all commands and must provide the status of each request back to the user or requesting system.

The AMI software management system must be able to display non-communicating endpoints and alarm conditions in a list and/or on a map.

The AMI software management system must provide performance metrics and monitoring tools that track the health of AMI system operations.

Network Management

The network management system must provide a centralized framework such that traffic for all applications can be effectively managed and secured under a single application.

The network management system must support the collection, filtering, and correlation of fault events from multiple network technologies (RF, cellular, etc.).

The network management system must display network endpoints on a GIS-based map.

The network management system must be able to interrogate the network endpoints on-demand to verify communications status (node ping).

The network management system must detect, filter, and report on non-communicating endpoints.

The network management system must be able to issue configuration updates to network endpoints over-the-air.

The network management system must be able to issue firmware updates to network endpoints over-the-air.

The AMI system must provide automatic authentication and authorization of any endpoint attempting to join the network.

Data Collection and Daily Operations

The AMI software management system must be capable of retrieving all available consumption, alarms, and event information from the AMI modules.

The solution must employ redundant communications to mitigate the need for retrieving missing historic data.

Endpoints must transmit data according to a pre-determined call-in schedule.

The AMI software management system must be capable of collecting time-stamped alarms and events with each scheduled read.

The AMI software management system must allow users to initiate on-demand requests for most recent reads.

The AMI software management system must support organizing multiple meters into single groups so utility operations such as scheduled meter readings can be performed on all AMI modules that share topology, geography, customer segmentation, billing cycle, etc.

The AMI software management system must support the ability to detect and issue alarms for consumer leak detection.

The AMI software management system must issue over-the-air firmware updates to targeted modules.

The AMI software management system must support the secure operation of a remote service valve operations

The AMI software management system must collect the AMI modules' read data four times per day.

The AMI software management system must store device interaction history and user interaction information for the purpose of audit history for a 30-day minimum.

The AMI software management system must support industry recognized protocols such as DLMS-COSEM.

The AMI software management system must support the ability to collect 15-minute interval data.

The AMI software management system must be able to remotely configure event logging and alarms.

The solution must be able to report critical alarm conditions in endpoint immediately upon occurrence.

The AMI software management system must report those meters that have not issued a data collection reading within a defined period (such as the last 24 hours, 3 days, 7 days, 30 days).

AMR Route Management

For instances where mobile or walk-by data collection may still be required, efficient route management is an essential requirement. For this reason, the proposed solution must offer the following features:

The system must be able to quickly plan, schedule, and manage efficient meter reading routes.

The system must use visualization tools, such as map-based views of metering service areas and individual meters, for planning, viewing, creating, and dispatching routes.

The system must track the workload and progress of groups of scheduled routes.

The system must automatically issue route assignments to meter readers based on read schedules, GPS meter locations, and designated meter reader working areas.

The system must let dispatchers quickly define new ad hoc meter reader working areas simply by drawing areas around map views of the service territory.

The system must allow users to automatically assign ad hoc routes to the appropriate meter reader based on their designated working areas.

The system must capture data from meters that are outside the range of the network, the system must allow meter readers to capture manual or radio reads for meters without a cellular AMI module.

The system must create ad-hoc routes based on any given report or query criteria.

The system must allow dispatchers to view the meters assigned to each meter reader and monitor the readers' progress throughout the workday in near real time.

The system must monitor each field team's reading progress via a simple dashboard.

To ensure field team safety, the system must have an option to receive regular location updates of their precise geographic locations at 5-minute intervals.

The system must identify those meters that failed validation based on a variety of criteria, such as abnormal consumption or tamper conditions. The system must have a dashboard view for displaying the most common validation metrics.

The system must be able to filter and create routes based on specific exceptions to dispatch field crews for investigation.

The system must allow a seamless migration from automated meter reading to AMI.

The system must be able to import and assign data collection routes from a legacy Itron AMR system.

The system must be able to create new data collection schedules for specific routes.

The system must be able to assign scheduled routes to appropriate meter readers.

The system must be able to assign routes in bulk using checkboxes.

The system must be able to export AMR reading export data to billing systems.

The system must allow users in the field to take advantage of Android, iOS, or Windows devices for AMR or manual meter reading.

Meter Data Management

The solution's software management system must support the following meter data management functions:

It must provide centralized long-term data storage.

It must validate incoming meter read data and accept or reject data according to utility preferences.

It must provide search and querying functions.

It must display and manage data, regardless of how was is collected (walk-by, drive-by, network).

It must track events and alarms reported by endpoints.

It must support automated billing schedule responses and workflows.

It must log, track, and audit data changes.

It must identify endpoints reporting a low battery.

It must perform device audits to identify and prioritize meter replacements.

It must display targeted endpoints on maps.

It must optimize routes for targeted endpoints for field service or AMR data collection.

Reporting

The system must come with a suite of standard reports regarding system performance, network health, meter reader efficiency, and utility assets that are reporting alarms and anomalies. Reporting must also support walk-by and drive-by AMR activities. Such reports must include:

A report that provides an overview of every meter in a mobile route, including the read collected, whether that read failed validation, and any comments or trouble codes that were entered.

A report that lists the unread meters for the selected collection schedule.

A report that lists mobile AMR reads.

A report that lists manual "walk-by" reads.

A report that lists those meters read for which the software management system does not have GPS coordinate information.

A report that summarizes any events that may require action on the part of the utility, such as leaks, tampers, reverse flow events, or validation failures.

A list of devices that reported leaks.

A list of devices that reported tamper events.

A list of meters skipped on a mobile reading tour.

A list of meters with no reported usage between reading tours.

A list of meters with a flow rate that differed from the expected flow.

A list of mobile readings that need extra attention and may be rescheduled.

A list of any read that came back with a comment or trouble code.

A list of any AMR reads that came back with a critical alarm associated with it, such as a Cut Cable alarm.

A list of manual reads that captured GPS coordinates a significant distance away from the location of the meter stored in the software management system.

A list of AMR meters that had to be read manually.

A list of reads where the entered read does not correspond to the format of the meter register. This requirement only applies outside of North America.

A report that shows total usage for every meter over the consumption period.

A list of all meters that failed Hi/Lo validation.

A list of those meters that failed Hi/Lo validation by a threshold amount.

A list of readings where the index value decreased over the consumption period but register rollover does not appear to be the cause.

The system must be able to query and filter data and save these query configurations as custom reports.

The system must be able to export report data in CSV format.

System Administration

The AMI software management system must log all actions taken by system users.

The AMI software management system must support Active Directory integration.

The AMI software management system must provide role-based access controls that define/restrict the features/functions available to authenticated entities.

The AMI software management system must support configurable password policies that can enforce the use of strong passwords.

Customer Service Representative (CSR) Tools

The solution must include user-friendly tools for use by our Customer Service Representatives (CSRs) so they can quickly locate and access detailed account information and promptly resolve common customer service issues.

CSRs must be able to view both summarized and detailed account information and usage data.

The system must allow for data to be presented in regionally appropriate units of measure.

Account and usage information must include the following details in a manner that is easy to locate and to interpret:

account and location information

applicable network data

schedules

the account's meter read history

detailed historic consumption data

large deviations in consumption

tamper events

meter and associated site photos

meter reader comments

other pertinent asset data

Customer Engagement Web Portal

Many customers want to take an active role in monitoring their gas usage behaviors and associated costs. To promote informed customers and the best possible customer service, the proposed solution must have some means to engage with our customers, such as a web portal. Such a solution must, at a minimum, meet the following requirements:

Customer must be able to access the solution from the smart phone, tablet, or PC of their choice.

The solution must provide customers with insights into their gas usage patterns in a manner that is easy to use and to understand, such as simple dashboards, graphs, and tables.

The solution must monitor the account's consumption over time.

The solution must be designed so that customers can monitor and manage their own usage and conservation efforts.

Customers must be able to configure their own parameter-based alarms for gas usage, and the solution must automatically notify them if they exceed these parameters.

The solution must include:

account information

historic consumption data

summary and detailed usage data

daily consumption

meter read history

Delivery Services

Solution Delivery

The Bidder must include the following solution implementation services:

Cellular coverage modelling

Project management

AMI software management system configuration

AMI software system testing

Back-office system integration and testing

Cellular Carrier

The Bidder must manage the relationship with the cellular network service provider on City of DeFuniak Springs's behalf to optimize network coverage, reliability, and cost.

Training

Training must include:

System Administrator Training

System User/Operator Training

Endpoint Device Field Tool Application Training

Hosting Environment and Managed Services

The AMI software management system must be available through a hosted software as a service (SaaS) subscription offering.

The SaaS subscription must include:

AMI software management system

Cellular endpoint connectivity (via cellular carrier)

Ongoing software system maintenance

Ongoing technical support services

The AMI software management system must support server virtualization.

The AMI software management system must be synchronized to an enterprise-approved time source.

Integration and Data Transfers

The AMI software management system must support batch data exports to other utility business systems via CSV.

As an option, the network management system must offer a northbound API to integrate with other utility systems.

The system must support file transfers that can be exported or downloaded through the software management system's user interface, via scheduled automated SFTP file transfers, or via automated API calls.

Security

Data Center Security and Hosting Operations

The solution's hosting center must provide security at the server, network, and storage levels.

The vendor's SaaS services and operations must be covered by a cybersecurity framework, such as ISO 27001:2022.

The solution's hosting center must complete an annual SOC 2 audit to validate that adequate operational processes are in place to provide system security and data privacy.

The solution's SaaS services and operations must be covered by SOC 1 Type 2 and SOC 2 Type 2 attestations.

The vendor must submit annual unqualified SOC 1 Type 2 and SOC2 Type 2 Reports.

AMI System Security

The AMI system must support device-level authentication.

The AMI system must be capable of encrypting data and commands at the network and application layers of the communications architecture.

The AMI system must authenticate back-office service requests.

The AMI system must use signed credentials for field tools that access network endpoints in the field.

The AMI system must use role-based access control to define/restrict the features/functions available to authenticated entities.

The AMI system must detect attempts by rogue devices to gain access to the communication network.

The AMI system must provide threshold-based rule processing for exception reporting.

Application Security

The software management system must support user authentication using Microsoft Active Directory through Windows or LDAP single sign-on technologies. (Ref: HTTPS, TLS, Encryption at rest and at transit is offered by Temetra)/ We support SSO via Azure active directory or OAuth 2.0)

The AMI software management system must provide role-based access controls (RBAC) that define and manage user access to the system's features and functions.

The AMI software management system must encrypt/decrypt data transmitted between the AMI modules and the software management system to ensure integrity and confidentiality of the data.

The AMI software management system must digitally sign all commands issued to the meters.

The AMI software management system must authenticate all service requests from back-office systems.

The AMI software management system must provide signed credentials for field tools that access meters in the field.

The AMI software management system must authenticate all AMI modules requesting access to the system using digital security material.

The AMI software management system must provide appropriate level of security material for all AMI modules such that compromising one device will not compromise the entire device population.

The AMI software management system must provide a centralized management tool for authorized personnel to manage the generation, secure storage, and backup/restoration of cryptographic security keys for AMI modules.

The AMI software management system must encrypt/decrypt critical data and commands between the AMI modules using AES-256-bit encryption.

TECHNICAL QUESTIONS

City of DeFuniak Springs requests that Bidders provide written responses to the following:

Software Management System

Describe the system's user interface and network management capabilities for all devices on the network. City of DeFuniak Springs prefers one network management system for all communication modules included in the solution. Include screenshots that show network status, key performance indicators, and troubleshooting tools in the user interface. If needed, include an attachment that illustrates the software management system's capabilities in detail.

Describe how the system supports monitoring system health.

Describe how the system supports monitoring system alarms and alerts.

Describe how the system supports move-in/move-out readings.

Describe how the system supports customer billing.

Describe how the system supports theft detection.

Describe how the system supports distribution loss analysis.

Describe how the system integrates gas metering into a single solution.

Describe how the system enables end customers to view their own usage information.

Describe the system's performance capabilities for collecting meter data.

Describe how the utility can determine that the system is functioning properly.

How does the system notify users of failed meter communications?

How does the system track device status change?

Describe how the system locates unread meters.

Describe how the system collects unread meter data.

Describe how does the system configures and reprograms meters/modules remotely.

Describe the software management system's data management capabilities.

Describe the data collection system's standard reports. Are they configurable and scheduled?

Discuss the software management system's scalability options.

Describe the different options to add new meters to the AMI system.

Field Tools

Describe the field installation tools and software used to install, program, audit, and maintain the devices in the field. Do these tools support "Bring your own devices" such as working with your iPhone or Android cell phones along with tablets and laptops?

Network Communications

Provide a diagram of the AMI system architecture.

Describe the endpoints' communication capabilities.

Include a network coverage study for the project.

Describe how the system supports two-way communications to the meters within City of DeFuniak Springs's service territory regardless of geographic or structural challenges and within a single software management system.

Describe the AMI system's process to upgrade device firmware remotely over-the-air (OTA) and locally in the field.

Describe the system's process to synchronize time for all solution components.

Proposed Meters and Modules

General Description

Describe the features and functions of the proposed remote gas AMI meter or module.

List all AMI module events and alarms transmitted to the HES.

What is the range of meter sizes available?

What is the anticipated battery life of the proposed meter and/or AMI module?

Summarize the manufacturer's product warranty covering the proposed AMI modules.

Provide a history for the past three years for units ordered, units delivered, units returned for warranty, and the overall failure rate for the meters and/or communication modules for the proposed solution.

Describe the product strategy and product roadmap for the next three years. Highlight any planned evolutions of current technology and provide a description of how future and current technologies will maintain compatibility and interoperability within your system.

System Integration and Interoperability

Describe the system's approach to interfacing with other utility systems. City of DeFuniak Springs prefers the system use open, published interface standards to ensure seamless integration with other business systems. Please list the interface standards supported by the solution.

Describe the standard interfaces you support for integrating with other back-office software systems such as CIS, MDMS, Asset Management, and Outage Management.

Does the AMI system support prebuilt integration software? Explain.

Describe any noteworthy integration challenges.

How does the Utility add custom integration functionality?

Security

Describe how the system provides a secure, two-way communications path between the City of DeFuniak Springs and IP-enabled meters, battery-powered endpoints, sensors, and other devices in the field.

Describe how the AMI system's security framework ensures the integrity and confidentiality of critical data and commands at the application level.

Describe how individual customer data is secured and separated in a hosted environment.

Describe how the proposed system supports Active Directory and Single Sign-On.

Describe how the solution secures firmware upgrades, both over-the-air and in the field.

Bidder Profile and Experience

Provide a company overview for the project's Prime and Subcontractors. Summarize your experience implementing similar solutions and scope to that being proposed.

Describe the roles, devices, and/or services of any third-party or subcontracting entities that will contribute to the project and their relationship to the Prime contractor.

Describe your approach to quality assurance, control, and continuous improvement. List any quality standards to which your company and facilities subscribe, including standards such as ISO 9001.

Provide three project references within the last five years that employ the same core solution, similar endpoint counts, and a similar overall project scope.

Deployment and Implementation Services

Provide a project organizational chart that shows the reporting structure of the Implementation Team, and summarize the responsibilities for each role.

Describe your project management and implementation methodology.

Describe your key project management deliverables.

Describe your project status reporting.

Provide a preliminary project implementation schedule that outlines the key project milestones.

Describe the device warranties and Return Material Authorization (RMA) procedure.

Describe the solution's Training Program.

Managed Services

City of DeFuniak Springs prefers a Software as a Service (SaaS) model. Please describe your SaaS capabilities, including cost savings to City, data center location for the proposed system, service levels, security provisions, and failover procedures.

The City of DeFuniak Springs may choose to procure a turnkey offering. Please describe your Network as a Service (NaaS) and Field Service (Network and Endpoint Management) options.

Describe the solution's maintenance and upgrade process.

Describe the solution's technical support channels.

Describe the technical support escalation process.

Describe the solution's cybersecurity framework for SaaS operations and provide copies of its associated certifications.