Request for Information (RFI) MFN3.pdf

4050 Esplanade Way

Tallahassee, FL 32399-0950 850-488-2786

Ron DeSantis, Governor

Tom Berger, Interim Secretary

REQUEST FOR INFORMATION (RFI)

MYFLORIDANET-3

RFI NO: DMS-25/26-253

THE STATE OF FLORIDA

DEPARTMENT OF MANAGEMENT SERVICES

REFER ALL INQUIRIES TO:

STEFANIE HIGGINS

DEPUTY DIRECTOR OF PROCUREMENT AND CONTRACT MANAGEMENT

DIVISION OF STATE PURCHASING

FLORIDA DEPARTMENT OF MANAGEMENT SERVICES

4050 ESPLANADE WAY, SUITE 360

TALLAHASSEE, FL 32399-0950

EMAIL: STEFANIE.HIGGINS@DMS.FL.GOV

THE SOLE PURPOSE OF THIS RFI IS TO OBTAIN INFORMATION FROM THE VENDOR

COMMUNITY. THE DEPARTMENT IS NOT SEEKING BIDS, OFFERS, OR PROPOSALS, AND NO

CONTRACT AWARD WILL RESULT FROM THIS RFI.

mailto:stefanie.higgins@dms.fl.gov

FLORIDA DEPARTMENT OF MANAGEMENT SERVICES

Request for Information

MyFloridaNet-3

DMS-25/26-253

I. INTRODUCTION

The State of Florida (State), Department of Management Services (Department), issues this Request for Information (RFI) to seek information from vendors regarding network infrastructure and support services for Eligible Users, including State agencies, county and city governments, school districts, universities, community colleges, and non-profit organizations. The information gathered from this RFI may be used to develop a future competitive solicitation.

II. PURPOSE OF AN RFI

Rule 60A-1.042, Florida Administrative Code (F.A.C.), provides that an agency may request information from the vendor community by issuing an RFI. Agencies are authorized to use RFIs for research to determine whether to competitively procure particular commodities or contractual services, which solicitation process to use for a particular need, and to research general, special, or technical specifications to be included in a solicitation. An RFI is not a “competitive solicitation,” as defined in section 287.012(6), Florida Statutes (F.S.). A vendor’s response to an RFI is not an offer to contract, and the agency may not use the vendor’s submission to justify a contract with that vendor without otherwise complying with Chapter 287, F.S. Vendors submitting a response to an agency’s RFI are not prohibited from responding to any related subsequent solicitation.

III. DEFINITIONS

Capitalized terms used in this RFI have the meanings set forth in this section or as otherwise defined elsewhere in this RFI, including within the provisions in which such terms are first used, unless the context clearly indicates otherwise.

1. Customer: As defined in Rule 60FF-1.002(1)(l), F.A.C.

2. DIVTEL: The Division of Telecommunications, within the Department.

3. Eligible User: As defined in Rule 60FF-1.002(1)(q), F.A.C.

4. MFN-2: MyFloridaNet-2. The current telecommunications network used by State agencies and other Eligible Users. The statewide infrastructure is designed to be a highly available, highly reliable, robust core that is able to support inter-site connections and access the Internet.

5. MFN-3: MyFloridaNet-3. The follow-on telecommunications network which will replace MyFloridaNet-2.

6. NOC: Network Operations Center. A collection of staff and support tools used to coordinate activities and provide 24x7x365 monitoring support for a statewide communications network.

7. SASE: Secure Access Service Edge. A cloud architecture model that combines network and security-as-a-service functions together and delivers them as a single cloud service.

Conceptually, SASE extends networking and security capabilities beyond where they're typically available.

8. SD-WAN: Software-Defined Wide Area Network. A virtual WAN architecture that allows the leveraging of any combination of transport services—including Multiprotocol Label Switching (MPLS), Long Term Evolution (LTE), and Dedicated Internet Access (DIA) services—to securely connect users to applications.

9. SOC: A centralized support unit on an organizational and technical level in a vendor’s organization to deal only with security issues.

10. VPN: Virtual Private Network. A computer network implemented in an additional software layer (overlay) on top of an existing larger network for the purpose of creating a private scope of computer communications or a secure extension of a private network into an insecure network such as the Internet.

11. VRF: Virtual Routing and Forwarding. A technology that allows multiple instances of a routing table to co-exist within the same router at the same time. Because the routing instances are independent, the same or overlapping IP addresses can be used without conflicting with each other.

12. WAN: Wide Area Network. A data network that covers a broad area; used to connect Local Area Networks (LANs) and other types of networks together, so that users and computers in one location can communicate with users and computers in other locations (i.e., any network whose communications links cross metropolitan, regional, state or national boundaries).

IV. BACKGROUND

The Department entered into the MFN-2 contract in 2016 to provide network services for Eligible Users, including State agencies, county and city governments, school districts, universities, community colleges, and non-profit organizations. MFN-2 is a multi-year contract for Florida providing a wide range of services, including core WAN, Metropolitan Area Network (MAN), and broadband solutions, all tailored to meet the diverse needs of its subscribers. These services are underpinned by stringent Service Level Agreements (SLAs) that guarantee availability, performance, and delivery expectations. MFN-2 offers flexible cloud connectivity solutions through Layer-2 and Layer-3 options. The Layer-2 service, designated as Cloud Connect 2 (CC2), provides dedicated point-to-point Ethernet connections to cloud providers, leveraging redundant Azure connections and optional dual links for other services at additional costs. The Layer-3 option, NetBond (NB3), facilitates Network Address Translation (NAT) and offers redundancy through AT&T's infrastructure in Orlando and Jacksonville, with a maximum bandwidth of 1 Gbps. The network also supports Interstate Services, enabling custom solutions for disaster recovery, SaaS integrations, or other needs that extend beyond Florida’s state boundaries.

Customer Premise Equipment (CPE) options under MFN-2 include contract-acquired devices with maintenance and installation services or Customer-provided hardware that meets specific requirements. Contract-acquired CPE offers a four-hour restoration SLA, provided Simple Network Management Protocol (SNMP) access is enabled. Customer-provided CPE must be certif ied, up-to-date, and configured by the Customer, with optional monitoring and management services available through the MFN-2 NOC.

Ancillary services under MFN-2 complement the core offerings, including expedited installations, data storage solutions, email and web hosting for e-rate eligible entities, and Managed Security Services (MSS). MSS encompasses capabilities such as event monitoring, vulnerability management, log retention, and advanced threat intelligence reporting. These comprehensive services, coupled with a focus on reliability and customer support, have made MFN-2 a critical backbone for State and local organizations.

The foundational features of MFN-2 provide a baseline for understanding the next iteration of the network, MFN-3, and the advancements it aims to introduce.

V. GOALS

The Department seeks information regarding reliable, efficient, user-friendly, and cost-effective network services that include the solutions and features listed below. When responding to this RFI, please consider the following solutions and features currently contemplated for inclusion in MFN-3, especially as they relate to the products and services your company currently offers.

• Layer 3 VPN (L3VPN)

• Virtual Private LAN Service (VPLS)

• VPN

o Client to LAN Multi-factor authentication (MFA) integration with Customer-supplied provider or vendor provided options.

o LAN to LAN o Must support VRF mapping

• Cloud Connect o Must support VRF mapping o Options should include Ethernet Virtual Circuits (EVCs) to core and EVC to Customer site (HQ/Datacenter).

• Centralized Firewall

• SLAs o Custom Performance SLAs on top of Availability SLAs

• Distributed Denial-of-Service (DDOS) Protection o Cloud only acceptable if all transit links are the same T1 provider and can scrub a /32 if a /32 cannot be scrubbed then local scrubbers are required.

o Cloud scrubbing for DIA/Transit services.

• Transit Internet o Single transit provider to facilitate cloud scrubbing for /32s.

Must have geo redundant peering locations to edge VRF.

• Local Loop o Must remain local.

o Must allow swap to another local loop provider for chronic issues.

• SDWAN

• SASE

• DIA

o Vendor provided address space for underlays.

o Vendor underlays must be packaged with DDOS.

• Point to Point o Wave o Virtual Private Wire Service (VPWS)

• MAN

o MAN boundaries will fall on Local Access and Transport Area (LATA) boundaries.

o Only needed if dedicated.

• NOC

• SOC

• Tools o Commercially provided Network Management System (NMS) o Role-Based Access Control (RBAC) for Department oversight of SUNCOM Customer base.

o Commercially provided Security Information and Event Management (SIEM) Assuming views and RBAC is strictly controlled.

• CPE

o Routers o Firewalls o SDWAN Appliances o Managed and unmanaged options o Full feature set supported

• Migration o Network-to-Network Interface (NNI) bridge between existing dedicated (MFN-2) and commercial.

o Each commercial vendor will pay for NNI bridge to MFN-2 dedicated.

VI. RESPONSE

To potentially develop a new solicitation for MyFloridaNet-3, the Department requests the following information:

Company Information: Company name, Primary contact, Address, Phone number, and email address

Considerations for Potential Solicitation:

A. Considering that there will be no guarantees regarding the number of circuits migrated, describe your proposed most cost-effective network for the State of Florida (dedicated, commercial, hybrid, etc.).

B. Could these services be provided in a statewide contract with multiple vendors awarded? If yes, describe how you would propose that these services be offered in a multiple award scenario? What are the drawbacks, if any, from this scenario?

C. For a multi-vendor award, how would you propose addressing compensation for managing interactions with another vendor’s NOC and SOC?

D. How would you propose operations for a single point of contact with a vendor’s NOC and SOC for a multi-award contract with distinct award categories?

E. Based on your proposed network, will network providers be willing to make DIVTEL the customer of record for last mile connections? How will this work for connections where the last mile is being resold by the network operator but provided by another entity?

F. Does your proposed solution provide a redundant EVC for Provider Edge (PE) diversity in the last mile/local loop?

G. What pricing structure is best suited to benefit the State of Florida?

H. Are availability and performance SLAs available for all required services?

a. If possible, please provide examples of the SLAs and notate if they are for dedicated, commercial, or a hybrid network.

I. DIVTEL must be part of the approval process for last mile selection when onboarding new circuits. Do you foresee any issues with this? If yes, please explain why.

J. DIVTEL must be given contact information for the providers of resold last mile circuits. Do you foresee any issues with this? If yes, please explain why.

K. Will all of DIVTEL’s services be deployed on commercial equipment or will some or all components be deployed on dedicated resources?

a. If components are to be deployed on dedicated resources, please (i) provide a list of such dedicated resources, and (ii) confirm that read access will be provided to DIVTEL for such dedicated resources.

VII. PROCESS

• Responses to this RFI will be reviewed by the Department for informational purposes only and will not result in the award of a contract.

• The Department is not required to utilize any responses to this RFI or any information gathered from such responses.

• Responding to this RFI does not prevent a vendor from being eligible to contract with the

Department (see section 287.057(19)(c), F.S., and Rule 60A-1.042(2), F.A.C.).

VIII. RESPONSE SUBMISSION AND DEADLINE

Please provide a response to this RFI electronically to the Stefanie Higgins at stefanie.higgins@dms.fl.gov by 5:00 p.m. ET on Friday, May 29, 2026.

In addition to responses to items A through K in Section VI. above, please include any written material that you would like the Department to consider in connection with this RFI.

IX. IDENTIFICATION AND PROTECTION OF CONFIDENTIAL INFORMATION

Article 1, section 24, of the Florida Constitution, guarantees every person access to public records, and section 119.011, F.S., provides a broad definition of “public record.” As such, responses to this RFI and any other records submitted to the Department are public records and are subject to disclosure unless exempt from disclosure by law. If the vendor considers any portion of a record it provides to the Department to be trade secret or otherwise confidential or exempt from disclosure under Florida or federal law (“Confidential Information”), the vendor shall mark as “confidential” each page of a document or specific portion of a document containing Confidential Information and simultaneously provide the Department with a separate, redacted copy of the record. The vendor shall state the basis of the exemption that the vendor contends is applicable to each portion of the record redacted, including the specific statutory citation for such exemption. The vendor shall only redact portions of records that it claims contains Confidential Information. If the vendor fails to mark a record it claims contains Confidential Information as “confidential,” or fails to submit a redacted copy in accordance with this section of a record it claims contains Confidential Information, the Department shall have no liability for release of such record. The foregoing will apply to every instance in which the vendor fails to both mark a record “confidential” and redact it in accordance with this section, regardless of whether the vendor may have properly marked and redacted the same or similar Confidential Information in another instance or record submitted to the Department.

In the event of a public records request, to which records the vendor marked as “confidential” are responsive to the request, the Department shall provide the vendor- redacted copy to the requestor.

If the vendor has marked a record as “confidential” but failed to provide a vendor-redacted copy to the Department, the Department may notify the vendor of the request and the vendor may have up to ten (10) Business Days from the date of the notice to provide a vendor-redacted copy, or else the Department may release the unredacted record to the requestor without liability. If the Department provides a vendor-redacted copy of the documents and the requestor asserts a right to the vendor-redacted Confidential Information, the Department shall promptly notify the vendor such an assertion has been made. The notice will provide that if the vendor seeks to protect the vendor-redacted Confidential Information from release it must, within thirty (30) days after the date of the notice and at its own expense, file a cause of action seeking a declaratory judgment that the information in question is exempt from section 119.07(1), F.S., or other applicable law and an order prohibiting the Department from publicly disclosing the information. The vendor shall provide written notice to the Department of any cause of action filed. If the vendor fails to file a cause of action mailto:Stefanie.higgins@dms.fl.gov within thirty (30) days, the Department may release the unredacted copy of the record to the requestor without liability.

If the Department is requested or compelled in any legal proceeding to disclose documents that are marked as “confidential” (whether by oral questions, interrogatories, requests for information or documents, subpoena, or similar process), unless otherwise prohibited by law, the Department shall give the vendor prompt written notice of the demand or request prior to disclosing any Confidential Information to allow the vendor to seek a protective order or other appropriate relief at the vendor’s sole discretion and expense. If the vendor fails to take appropriate and timely action to protect the Confidential Information contained within documents it has marked as “confidential” or fails to provide a redacted copy that may be disclosed, the Department may provide the unredacted records in response to the demand without liability.

The vendor shall protect, defend, and indemnify the Department for all claims, costs, f ines, settlement fees, and attorneys’ fees, at both the trial and appellate levels, arising from or relating to the vendor’s determination that its records contain Confidential Information. In the event of a claim brought against the Department for failure to release the vendor’s redacted Confidential Information, the vendor shall assume, at its sole expense, the defense or settlement of such claim, including attorney’s fees and costs at both the trial and appellate levels. If the vendor fails to continuously undertake the defense or settlement of such claim or if the vendor and Department mutually agree that the Department is best suited to undertake the defense or settlement, the Department will have the right, but not the obligation, to undertake the defense or settlement of such claim, at its discretion. The vendor shall be bound by any defense or settlement the Department may make as to such claim, and the vendor agrees to reimburse the Department for the expense, including reasonable attorney’s fees and costs at both the trial and appellate levels associated with any defense or settlement that the Department may undertake to defend vendor’s Confidential Information. The Department will also be entitled to join the vendor in any claim for the purpose of enforcing any right of indemnity under this section.

X. VENDOR COSTS

Vendors are responsible for all costs associated with the preparation, submission, and any potential meeting to discuss this RFI. The Department will not be responsible for any vendor related costs associated with responding to this request.

XI. DEPARTMENT CONTACT

If you have any inquiries concerning this RFI, please contact:

Stefanie Higgins Deputy Director of Procurement and Contract Management Florida Department of Management Services Division of State Purchasing 4050 Esplanade Way Tallahassee, Florida 32399-0950 Phone: (850) 487-3977 stefanie.higgins@dms.fl.gov mailto:stefanie.higgins@dms.fl.gov