Attachment J-Evaluator Scoresheet.xlsx

XLSX spreadsheet 34 KB Posted

Attached to
MyFloridaNet-3 Core Services - ITN
Solicitation number
ITN-12980
Issued by
Clay County, Leon County, Polk County, Florida

About this file

This document is an Evaluator Scoresheet for the Florida Department of Management Services' MyFloridaNet-3 (MFN-3) Core Services Invitation to Negotiate (ITN No. DMS-24/25-260), which seeks a comprehensive statewide telecommunications network infrastructure provider. The solicitation targets a single core services provider to design, implement, and manage a highly available network supporting approximately 3,500 connections for state agencies, eligible non-profits, and governmental entities in Clay, Leon, and Polk Counties. The contract will provide core network services including MPLS, internet access, VPN, SD-WAN, security services, and centralized network management, with an initial seven-year term that includes an 18-month migration period. Proposals are due by September 22, 2025, with an anticipated contract award in June 2026.

The evaluation methodology allocates 3,000 points (60%) for technical responses and 2,000 points (40%) for cost replies, with scoring across categories like staffing plans, network security, core functionality, operational management, and migration planning. The estimated annual enterprise expenditure is approximately $60 million, though this represents no guaranteed minimum spend. The contract includes a $60 million performance bond requirement and mandates compliance with Universal Service Fund regulations. Pricing will be based on a wholesale model with a DMS administrative fee, and services will be available on a month-to-month basis without quantity commitments or revenue guarantees. The current MFN-2 contract was previously held by L3Harris Technologies, and the new MFN-3 contract aims to reduce service costs, improve service quality, and increase long-term value for the state.

View the file

Other files

File Type Posted
Attachment E-Reply Format.pdf PDF
Attachment O-Price Evaluation Workbook.xlsx XLSX spreadsheet
FORM 12-PUR 1355 FOREIGN COUNTRY OF CONCERN ATTESTATION.pdf PDF
FORM 13-PUR 1808 COMMON CARRIER OR CONTRACTED CARRIER ATTESTATION.pdf PDF
Attachment E-Reply Format.pdf PDF
Attachment G-Instructions for Cost Reply Price Workbook.pdf PDF
Attachment H-Staffing Plan Worksheets.xlsx XLSX spreadsheet
Attachment I-Assumptions and Exceptions_v2 posted 6-30-25.docx DOCX document
Attachment M-Points Table.xlsx XLSX spreadsheet
Attachment O-Price Evaluation Workbook.xlsx XLSX spreadsheet
FORM 06–QUALIFICATIONS & EXPERIENCE QUESTIONNAIRE_v2 posted 6-30-25.docx DOCX document
Attachment A-Statement of Work_v2 posted 6-30-25.docx DOCX document
Attachment F-Technical Reply Instructions.pdf PDF
Attachment G-Instructions for Cost Reply Price Workbook.pdf PDF
Attachment J-Evaluator Scoresheet.xlsx XLSX spreadsheet
Attachment O-Price Evaluation Workbook.xlsx XLSX spreadsheet
FORM 10-CERTIFICATION OF DRUG-FREE WORKPLACE PROGRAM.pdf PDF
FORM 13-PUR 1808 COMMON CARRIER OR CONTRACTED CARRIER ATTESTATION.pdf PDF
Attachment A-Statement of Work_v3.docx DOCX document
Attachment L-Evaluator Instructions-Technical Reply.pdf PDF
Attachment O-Price Evaluation Workbook.xlsx XLSX spreadsheet
FORM 04-STATEMENT OF NO PRIOR DISQUALIFYING INVOLVEMENT.pdf PDF
FORM 05–MANDATORY RESPONSIVE REQUIREMENTS.pdf PDF
FORM 09-PUR 2024 USE OF COERCION FOR LABOR AND SERVICES.pdf PDF
FORM 12-PUR 1355 FOREIGN COUNTRY OF CONCERN ATTESTATION.pdf PDF
Addendum No. 1 - posted 6-30-25.pdf PDF
Attachment C-Service Level Agreements_v2 posted 6-30-25.xlsx XLSX spreadsheet
Attachment F-Technical Reply Instructions.pdf PDF
Attachment G-Instructions for Cost Reply Price Workbook.pdf PDF
Attachment L-Evaluator Instructions-Technical Reply.pdf PDF
Attachment N-Negotiator Scoring Sheet.xlsx XLSX spreadsheet
FORM 01–CONTACT INFORMATION.pdf PDF
FORM 12-PUR 1355 FOREIGN COUNTRY OF CONCERN ATTESTATION.pdf PDF
Addendum No. 1 - posted 6-30-25.pdf PDF
Addendum_No_2_posted_8-11-25.pdf PDF
Attachment H-Staffing Plan Worksheets v2.xlsx XLSX spreadsheet
Attachment L-Evaluator Instructions-Technical Reply.pdf PDF
Attachment M-Points Table.xlsx XLSX spreadsheet
Attachment O-Price Evaluation Workbook.xlsx XLSX spreadsheet
FORM 01–CONTACT INFORMATION.pdf PDF
FORM 05–MANDATORY RESPONSIVE REQUIREMENTS.pdf PDF
FORM 07–CLIENT REFERENCE FORM.pdf PDF
FORM 09-PUR 2024 USE OF COERCION FOR LABOR AND SERVICES.pdf PDF
Q&A_and_Addendum_No_3 posted_08-27-25.pdf PDF
_MFN-3_ITN_Core_Services_DMS-2425-260.pdf PDF
Attachment B-Draft Contract.pdf PDF
Attachment C-Service Level Agreements.xlsx XLSX spreadsheet
Attachment K-Cost Reply Price Workbook.xlsx XLSX spreadsheet
Attachment M-Points Table.xlsx XLSX spreadsheet
Attachment N-Negotiator Scoring Sheet.xlsx XLSX spreadsheet
Show 40 more

50 files listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Sheet1

ATTACHMENT J - EVALUATOR SCORESHEET ITN No. DMS-24/25-260 MyFloridaNet-3 Core ServicesEvaluator
Statement of Work Section/ Subsection Number and DescriptionRESPONDENT 1RESPONDENT 2RESPONDENT 3RESPONDENT 4RESPONDENT 5
All subsection responses are valued equally . R&C are Read and Comply; NR are No Response Required
SECTION 1.0Introduction and DefinitionsPoints Per Sectionst
1.1IntroductionNR
1.2DefinitionsNR
SECTION 2.0SCOPE OF WORK (TECHNICAL SOLUTION)2000st-----
2.1Staffing Plans100st-----
2.1.1Overall Staffing Plan
2.1.2Staffing - Local Service Availability
2.1.3Contractor Staffing Responsibilities
2.1.4Ensuring Sufficient and Qualified Staff
2.1.5Support Staffing
2.1.6Staff Sub-contractingR&C
2.2Qualifications for Prime Respondent and Subcontractors50st-----
2.2.1Business Proposal
2.2.2Ability to Perform – Business Focus
2.2.3Ability to Perform – Technical Focus
2.2.4Dispute History
2.2.5Experience for Enterprise Service Contracts
2.3General Requirements50st-----
2.3.1Use of Manufacturer’s Descriptive TextR&C
2.3.2Flexibility to Quickly Modify Services
2.3.3Service Testing RequirementsR&C
2.3.4Non-standards-based service
2.3.5Operational and Contractual Oversight RoleR&C
2.3.6Core Services ProviderR&C
2.3.7Training on MFN-3 Technologies, Tools, and Services
2.3.8Administrative Support and Technical Refresh
2.3.9Support for Team Collaboration Tool
2.3.10Inspection Process
2.3.11Logging by Default
2.3.12Operational MeetingsR&C
2.3.13Surcharges and Fees
2.3.14Naming Conventions
2.3.15Network Time Service
2.3.16Continuity of Operations Plan
2.3.17Growth Planning
2.4Wide Area Network Enterprise Security Services280st-----
2.4.1Enterprise Firewall Functionality
2.4.2General Description - Operational Aspects of the Wide Area Network Enterprise Security Service
2.4.3Security Operations Center (SOC)
2.4.4Enterprise Security Information Event Manager Tool
2.4.5Authentication Service
2.4.6Assisting DMS in its Efforts Related to Security Compliance Audits, Training, and Awareness
2.4.7Operational and Security Review of Logs and Interpretation of Traffic FlowsR&C
2.4.8Security Logging Functionality and Review Strategies
2.4.9Proactive and Reactive Security
2.4.10Denial of Service and Distributed Denial of Service Protection as a Service
2.4.11Attack Types
2.4.12Mitigation of DoS AttacksR&C
2.4.13Individual IP Address Granularity needed for Mitigation of DoS AttacksR&C
2.4.14Individual IP Address Granularity and Maintaining Those AddressesR&C
2.4.15Denial of Service Customer ProfileR&C
2.4.16Notifications Sent from the System
2.4.17Real-time Access to a Robust Reporting Dashboard (Customer Portal)
2.5Universal Service Fund100st-----
2.5.1Maintaining Florida’s E-rate Eligibility under MyFloridaNet-3R&C
2.5.2Core Service Provider’s Liability for Maintaining Eligibility as a USF Service ProviderR&C
2.5.3Eligibility under the USF E-rate programR&C
2.5.4E-rate Experience
2.5.5E-rate Customer CareR&C
2.5.6E-rate BillingR&C
2.6Business Operations-Requirements0R&C
2.7Core Functionality and Related Services420st-----
2.7.1General Core and Backbone Design RequirementsR&C
2.7.2Description of Proposed IP Core and Backbone
2.7.3MFN-3 Services Infrastructure Build-out PlanR&C
2.7.4Description of Proposed Virtual Routing and Forwarding (VRF) Structure(s)
2.7.5Management VRF Strategy and Structure
2.7.6SLA Core Probes
2.7.7Core Support for IPv6 Protocol and the DMS Addressing Plan
2.7.8Core Node Infrastructure
2.7.9Capability of Core Infrastructure
2.7.10Core Internet
2.7.11Internet Exchange Peering
2.7.12Operational and Technical Support for MFN-3 Transport Services Providers
2.7.13Enterprise Quality of Service (QoS)R&C
2.7.14MPLS
2.7.15Multicast Functionality
2.7.16MFN-3 Services Infrastructure Build-Out Plan Narrative
2.7.17Highly Available Highly Reliable Design CharacteristicsR&C
2.7.18High Availability and High Reliability Strategy for the Core and Backbone
2.7.19Physical Security as a component of High Availability and High Reliability
2.7.20Power Supply as a component of High Availability and High Reliability
2.7.21Minimal Convergence Times as a component of High Availability and High Reliability
2.8Daily Operational Management, Tools, and NOC300st-----
2.8.1Day-to-day Responsibility is Provided by the Core Services Provider and its SubcontractorsR&C
2.8.2Scope of Operational Management (Operational Support)R&C
2.8.3Network Operations Center
2.8.4Core Service Provider’s Network Operations Center Implementation and FunctionalityR&C
2.8.5DMS Network Operations Center Oversight Responsibilities
2.8.6Maintenance Notifications and Change Control Processes
2.8.7Proposed Escalation Process
2.8.8Change Control Coordination among Providers
2.8.9Seamless Operational Day-To-Day Services
2.8.10Effective Operational Management within Logical Partitions
2.8.11NMS and Security Tools Access
2.8.12Internet Access to Tools
2.8.13Customer Segregated NMS Views
2.8.14Sharing Management Tools
2.8.15Time stampsR&C
2.8.16Special Handling for Public SafetyR&C
2.8.17Ticket Classifications Based on Problem SeverityR&C
2.8.18Reporting and Screen Viewing FunctionalityR&C
2.8.19Proposed Ticketing System
2.8.20Proposed Logging and Archival Process
2.8.21Proposed Traffic Analyzer
2.8.22Proposed SLA Performance Monitoring Service Functionality
2.8.23Proposed Configuration Management System
2.8.24Proposed Command Line Interface (CLI) and SNMP Access
2.8.25Proposed Network Management System (NMS)
2.8.26Proposed Performance Tools
2.8.27Proposed Diagnostics Tools
2.8.28Proposed IP Address Management (IPAM) Tool
2.9Current MyFloridaNet Tools0NR
2.10Customer Premises Equipment – General100st-----
2.10.1Acquisition and Support Specifications for Equipment Supported Under MFN-2
2.10.2Authentication, Authorization, And Accounting (AAA)R&C
2.10.3Customer Premises Equipment RoadmapR&C
2.10.4Roadmap ProcessR&C
2.10.5Bi-directional Forwarding Detection (BFD)R&C
2.10.6Operational Parameters Related to Customer-Managed Router ConfigurationR&C
2.10.7Core Services Provider-Managed Configuration Management Support - StandardR&C
2.10.8Virtual Routing and Forwarding (VRF)-Enabled CPE and Multi-VRF Configuration SupportR&C
2.10.9Customer Premises Equipment Response Requirements
2.11Remote Access -- Centralized Virtual Private Network100st-----
2.11.1Centralized VPN Service for MFN-2 Remote AccessR&C
2.11.2Remote Site to Centralized VPN Gateway (LAN-to-LAN VPN)
2.11.3Redundancy for the Centralized VPN System Components
2.11.4Remote User Access Control MechanismsR&C
2.11.5Network Address Translation (NAT)
2.11.6Installation, Monitoring Trouble Reporting for LAN-to-LAN VPNR&C
2.11.7IKE, IPSec Security Association (SA) and SSL Attribute Matrix
2.11.8Client to LAN Remote User to Centralized VPN Gateway (Client-to-LAN VPN)
2.11.9Client-to-LAN VPN Split-Tunneling and Security Policy Compliance
2.11.10Multi-Factor Authentication Requirement
2.11.11Username/Password Policy EnforcementR&C
2.11.12Inactivity and Duration Timeouts for Client and Clientless (SSL) Sessions
2.11.13In Case of Emergency (ICE) VPN AccountsR&C
2.11.14Test VPNs for DMSR&C
2.11.15End-to-end Integration ResponsibilityR&C
2.11.16VPN Customer MigrationR&C
2.12General Specifications, Types of Services and Associated Components100st-----
2.12.1Strategies to Promote and Incorporate Access ProvidersR&C
2.12.2End-To-End Integration
2.12.3Multiple Paths Support Into Core
2.12.4Access to MFN-3 via VPN Tunnel (AMVT) Services
2.12.5AMVT Monitoring and Operational Management
2.13SD-WAN Software Defined Wide Area Network100st-----
2.13.1SD-WAN Service for MFN-3 Access
2.14SASE Secure Access Service Edge100st-----
2.14.1SASE Service for MFN-3 Access
2.15Cloud Transport50-----
2.15.1Cloud Transport Services
2.16Ancillary Network Services – GeneralNR
2.17Miscellaneous ConditionsNR
2.18Project Management150-----
2.18.1Project Charter and Project Management Plan
2.18.2Project Management Implementation Phase
2.18.3Project Mangement - Guides
2.18.4Project Mangement - Closure
2.18.5Project Managrement Implementation and Migration Plans
SECTION 3.0Performance Measures (Service Level Agreements - SLAs )250st-----
3.1Performance Measures250st-----
3.1.1SLA CriteriaR&C
3.1.2Performance Monitoring BaselineR&C
3.1.3Scrubbing Alerts
3.1.4Dynamic SLAs
3.1.5Timely Credit Determination and the Application of Credits
3.1.6Scrubbing Alerts Production Implementation
SECTION 4.0Financial Consequences for Non-Performance0st-----
4.1Withholding Payment or Other RemediesR&C-----
SECTION 5.0Migration and Transition Planning (Support Services)750st-----
5.1Migration from MFN2 to MFN-3750st-----
5.1.1MFN-3 Core Services Readiness Plan
5.1.2Migration Plan – Sites and Services
5.1.3Migration - Staffing Resource Requirements
5.1.4Migration - Knowledge Transfer
5.1.5Migration - Project Management Tasks and Related Deliverables
5.1.6Migration - Engineering Review
5.1.7Migration - Provision Planning
5.1.8Migration - Network Operations Center
5.1.9Migration - Administrative Services
5.1.10Migration - Payment Strategy Connection-By-ConnectionR&C
5.1.11Migration - Connection Testing Period with Fall Back OptionR&C
5.2Transition between MFN-2 and the Successor ContractNR-----
Technical EvaluationTechnical Evaluation3,000.00st-----

Evaluator's Name

Date

File details come from the government source that posted it. Updated .