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
The document is an Evaluator Scoresheet for Invitation to Negotiate (ITN) No. DMS-24/25-260 for MyFloridaNet-3 Core Services, issued by the Florida Department of Management Services (DMS). The scoresheet outlines a comprehensive evaluation framework for potential respondents across multiple technical and operational sections, including staffing plans, qualifications, network security services, universal service fund compliance, core functionality, operational management, customer premises equipment, remote access, and migration planning. The total possible technical evaluation points are 3,000, with significant point allocations for sections like Wide Area Network Enterprise Security Services (280 points), Core Functionality and Related Services (420 points), Daily Operational Management, Tools, and Network Operations Center (300 points), and Migration and Transition Planning (750 points).
The scoresheet indicates a complex, multi-phase procurement for a state-wide network infrastructure service, with detailed requirements for technical capabilities, security protocols, operational support, and transition management. While specific pricing details are not provided in this evaluation document, the extensive scoring criteria suggest a rigorous selection process focused on comprehensive technical capabilities, operational excellence, security preparedness, and successful migration strategy. The evaluation approach allows for a holistic assessment of respondents' abilities to deliver a robust, secure, and flexible network infrastructure for Florida's government and educational institutions.
View the file
Other files
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 Services | Evaluator | ||||
| Statement of Work Section/ Subsection Number and Description | RESPONDENT 1 | RESPONDENT 2 | RESPONDENT 3 | RESPONDENT 4 | RESPONDENT 5 |
| All subsection responses are valued equally . R&C are Read and Comply; NR are No Response Required | ||||||||
| SECTION 1.0 | Introduction and Definitions | Points Per Section | st | |||||
| 1.1 | Introduction | NR | ||||||
| 1.2 | Definitions | NR | ||||||
| SECTION 2.0 | SCOPE OF WORK (TECHNICAL SOLUTION) | 2000 | st | - | - | - | - | - |
| 2.1 | Staffing Plans | 100 | st | - | - | - | - | - |
| 2.1.1 | Overall Staffing Plan | |||||||
| 2.1.2 | Staffing - Local Service Availability | |||||||
| 2.1.3 | Contractor Staffing Responsibilities | |||||||
| 2.1.4 | Ensuring Sufficient and Qualified Staff | |||||||
| 2.1.5 | Support Staffing | |||||||
| 2.1.6 | Staff Sub-contracting | R&C | ||||||
| 2.2 | Qualifications for Prime Respondent and Subcontractors | 50 | st | - | - | - | - | - |
| 2.2.1 | Business Proposal | |||||||
| 2.2.2 | Ability to Perform – Business Focus | |||||||
| 2.2.3 | Ability to Perform – Technical Focus | |||||||
| 2.2.4 | Dispute History | |||||||
| 2.2.5 | Experience for Enterprise Service Contracts | |||||||
| 2.3 | General Requirements | 50 | st | - | - | - | - | - |
| 2.3.1 | Use of Manufacturer’s Descriptive Text | R&C | ||||||
| 2.3.2 | Flexibility to Quickly Modify Services | |||||||
| 2.3.3 | Service Testing Requirements | R&C | ||||||
| 2.3.4 | Non-standards-based service | |||||||
| 2.3.5 | Operational and Contractual Oversight Role | R&C | ||||||
| 2.3.6 | Core Services Provider | R&C | ||||||
| 2.3.7 | Training on MFN-3 Technologies, Tools, and Services | |||||||
| 2.3.8 | Administrative Support and Technical Refresh | |||||||
| 2.3.9 | Support for Team Collaboration Tool | |||||||
| 2.3.10 | Inspection Process | |||||||
| 2.3.11 | Logging by Default | |||||||
| 2.3.12 | Operational Meetings | R&C | ||||||
| 2.3.13 | Surcharges and Fees | |||||||
| 2.3.14 | Naming Conventions | |||||||
| 2.3.15 | Network Time Service | |||||||
| 2.3.16 | Continuity of Operations Plan | |||||||
| 2.3.17 | Growth Planning | |||||||
| 2.4 | Wide Area Network Enterprise Security Services | 280 | st | - | - | - | - | - |
| 2.4.1 | Enterprise Firewall Functionality | |||||||
| 2.4.2 | General Description - Operational Aspects of the Wide Area Network Enterprise Security Service | |||||||
| 2.4.3 | Security Operations Center (SOC) | |||||||
| 2.4.4 | Enterprise Security Information Event Manager Tool | |||||||
| 2.4.5 | Authentication Service | |||||||
| 2.4.6 | Assisting DMS in its Efforts Related to Security Compliance Audits, Training, and Awareness | |||||||
| 2.4.7 | Operational and Security Review of Logs and Interpretation of Traffic Flows | R&C | ||||||
| 2.4.8 | Security Logging Functionality and Review Strategies | |||||||
| 2.4.9 | Proactive and Reactive Security | |||||||
| 2.4.10 | Denial of Service and Distributed Denial of Service Protection as a Service | |||||||
| 2.4.11 | Attack Types | |||||||
| 2.4.12 | Mitigation of DoS Attacks | R&C | ||||||
| 2.4.13 | Individual IP Address Granularity needed for Mitigation of DoS Attacks | R&C | ||||||
| 2.4.14 | Individual IP Address Granularity and Maintaining Those Addresses | R&C | ||||||
| 2.4.15 | Denial of Service Customer Profile | R&C | ||||||
| 2.4.16 | Notifications Sent from the System | |||||||
| 2.4.17 | Real-time Access to a Robust Reporting Dashboard (Customer Portal) | |||||||
| 2.5 | Universal Service Fund | 100 | st | - | - | - | - | - |
| 2.5.1 | Maintaining Florida’s E-rate Eligibility under MyFloridaNet-3 | R&C | ||||||
| 2.5.2 | Core Service Provider’s Liability for Maintaining Eligibility as a USF Service Provider | R&C | ||||||
| 2.5.3 | Eligibility under the USF E-rate program | R&C | ||||||
| 2.5.4 | E-rate Experience | |||||||
| 2.5.5 | E-rate Customer Care | R&C | ||||||
| 2.5.6 | E-rate Billing | R&C | ||||||
| 2.6 | Business Operations-Requirements | 0 | R&C | |||||
| 2.7 | Core Functionality and Related Services | 420 | st | - | - | - | - | - |
| 2.7.1 | General Core and Backbone Design Requirements | R&C | ||||||
| 2.7.2 | Description of Proposed IP Core and Backbone | |||||||
| 2.7.3 | MFN-3 Services Infrastructure Build-out Plan | R&C | ||||||
| 2.7.4 | Description of Proposed Virtual Routing and Forwarding (VRF) Structure(s) | |||||||
| 2.7.5 | Management VRF Strategy and Structure | |||||||
| 2.7.6 | SLA Core Probes | |||||||
| 2.7.7 | Core Support for IPv6 Protocol and the DMS Addressing Plan | |||||||
| 2.7.8 | Core Node Infrastructure | |||||||
| 2.7.9 | Capability of Core Infrastructure | |||||||
| 2.7.10 | Core Internet | |||||||
| 2.7.11 | Internet Exchange Peering | |||||||
| 2.7.12 | Operational and Technical Support for MFN-3 Transport Services Providers | |||||||
| 2.7.13 | Enterprise Quality of Service (QoS) | R&C | ||||||
| 2.7.14 | MPLS | |||||||
| 2.7.15 | Multicast Functionality | |||||||
| 2.7.16 | MFN-3 Services Infrastructure Build-Out Plan Narrative | |||||||
| 2.7.17 | Highly Available Highly Reliable Design Characteristics | R&C | ||||||
| 2.7.18 | High Availability and High Reliability Strategy for the Core and Backbone | |||||||
| 2.7.19 | Physical Security as a component of High Availability and High Reliability | |||||||
| 2.7.20 | Power Supply as a component of High Availability and High Reliability | |||||||
| 2.7.21 | Minimal Convergence Times as a component of High Availability and High Reliability | |||||||
| 2.8 | Daily Operational Management, Tools, and NOC | 300 | st | - | - | - | - | - |
| 2.8.1 | Day-to-day Responsibility is Provided by the Core Services Provider and its Subcontractors | R&C | ||||||
| 2.8.2 | Scope of Operational Management (Operational Support) | R&C | ||||||
| 2.8.3 | Network Operations Center | |||||||
| 2.8.4 | Core Service Provider’s Network Operations Center Implementation and Functionality | R&C | ||||||
| 2.8.5 | DMS Network Operations Center Oversight Responsibilities | |||||||
| 2.8.6 | Maintenance Notifications and Change Control Processes | |||||||
| 2.8.7 | Proposed Escalation Process | |||||||
| 2.8.8 | Change Control Coordination among Providers | |||||||
| 2.8.9 | Seamless Operational Day-To-Day Services | |||||||
| 2.8.10 | Effective Operational Management within Logical Partitions | |||||||
| 2.8.11 | NMS and Security Tools Access | |||||||
| 2.8.12 | Internet Access to Tools | |||||||
| 2.8.13 | Customer Segregated NMS Views | |||||||
| 2.8.14 | Sharing Management Tools | |||||||
| 2.8.15 | Time stamps | R&C | ||||||
| 2.8.16 | Special Handling for Public Safety | R&C | ||||||
| 2.8.17 | Ticket Classifications Based on Problem Severity | R&C | ||||||
| 2.8.18 | Reporting and Screen Viewing Functionality | R&C | ||||||
| 2.8.19 | Proposed Ticketing System | |||||||
| 2.8.20 | Proposed Logging and Archival Process | |||||||
| 2.8.21 | Proposed Traffic Analyzer | |||||||
| 2.8.22 | Proposed SLA Performance Monitoring Service Functionality | |||||||
| 2.8.23 | Proposed Configuration Management System | |||||||
| 2.8.24 | Proposed Command Line Interface (CLI) and SNMP Access | |||||||
| 2.8.25 | Proposed Network Management System (NMS) | |||||||
| 2.8.26 | Proposed Performance Tools | |||||||
| 2.8.27 | Proposed Diagnostics Tools | |||||||
| 2.8.28 | Proposed IP Address Management (IPAM) Tool | |||||||
| 2.9 | Current MyFloridaNet Tools | 0 | NR | |||||
| 2.10 | Customer Premises Equipment – General | 100 | st | - | - | - | - | - |
| 2.10.1 | Acquisition and Support Specifications for Equipment Supported Under MFN-2 | |||||||
| 2.10.2 | Authentication, Authorization, And Accounting (AAA) | R&C | ||||||
| 2.10.3 | Customer Premises Equipment Roadmap | R&C | ||||||
| 2.10.4 | Roadmap Process | R&C | ||||||
| 2.10.5 | Bi-directional Forwarding Detection (BFD) | R&C | ||||||
| 2.10.6 | Operational Parameters Related to Customer-Managed Router Configuration | R&C | ||||||
| 2.10.7 | Core Services Provider-Managed Configuration Management Support - Standard | R&C | ||||||
| 2.10.8 | Virtual Routing and Forwarding (VRF)-Enabled CPE and Multi-VRF Configuration Support | R&C | ||||||
| 2.10.9 | Customer Premises Equipment Response Requirements | |||||||
| 2.11 | Remote Access -- Centralized Virtual Private Network | 100 | st | - | - | - | - | - |
| 2.11.1 | Centralized VPN Service for MFN-2 Remote Access | R&C | ||||||
| 2.11.2 | Remote Site to Centralized VPN Gateway (LAN-to-LAN VPN) | |||||||
| 2.11.3 | Redundancy for the Centralized VPN System Components | |||||||
| 2.11.4 | Remote User Access Control Mechanisms | R&C | ||||||
| 2.11.5 | Network Address Translation (NAT) | |||||||
| 2.11.6 | Installation, Monitoring Trouble Reporting for LAN-to-LAN VPN | R&C | ||||||
| 2.11.7 | IKE, IPSec Security Association (SA) and SSL Attribute Matrix | |||||||
| 2.11.8 | Client to LAN Remote User to Centralized VPN Gateway (Client-to-LAN VPN) | |||||||
| 2.11.9 | Client-to-LAN VPN Split-Tunneling and Security Policy Compliance | |||||||
| 2.11.10 | Multi-Factor Authentication Requirement | |||||||
| 2.11.11 | Username/Password Policy Enforcement | R&C | ||||||
| 2.11.12 | Inactivity and Duration Timeouts for Client and Clientless (SSL) Sessions | |||||||
| 2.11.13 | In Case of Emergency (ICE) VPN Accounts | R&C | ||||||
| 2.11.14 | Test VPNs for DMS | R&C | ||||||
| 2.11.15 | End-to-end Integration Responsibility | R&C | ||||||
| 2.11.16 | VPN Customer Migration | R&C | ||||||
| 2.12 | General Specifications, Types of Services and Associated Components | 100 | st | - | - | - | - | - |
| 2.12.1 | Strategies to Promote and Incorporate Access Providers | R&C | ||||||
| 2.12.2 | End-To-End Integration | |||||||
| 2.12.3 | Multiple Paths Support Into Core | |||||||
| 2.12.4 | Access to MFN-3 via VPN Tunnel (AMVT) Services | |||||||
| 2.12.5 | AMVT Monitoring and Operational Management | |||||||
| 2.13 | SD-WAN Software Defined Wide Area Network | 100 | st | - | - | - | - | - |
| 2.13.1 | SD-WAN Service for MFN-3 Access | |||||||
| 2.14 | SASE Secure Access Service Edge | 100 | st | - | - | - | - | - |
| 2.14.1 | SASE Service for MFN-3 Access | |||||||
| 2.15 | Cloud Transport | 50 | - | - | - | - | - | |
| 2.15.1 | Cloud Transport Services | |||||||
| 2.16 | Ancillary Network Services – General | NR | ||||||
| 2.17 | Miscellaneous Conditions | NR | ||||||
| 2.18 | Project Management | 150 | - | - | - | - | - | |
| 2.18.1 | Project Charter and Project Management Plan | |||||||
| 2.18.2 | Project Management Implementation Phase | |||||||
| 2.18.3 | Project Mangement - Guides | |||||||
| 2.18.4 | Project Mangement - Closure | |||||||
| 2.18.5 | Project Managrement Implementation and Migration Plans | |||||||
| SECTION 3.0 | Performance Measures (Service Level Agreements - SLAs ) | 250 | st | - | - | - | - | - |
| 3.1 | Performance Measures | 250 | st | - | - | - | - | - |
| 3.1.1 | SLA Criteria | R&C | ||||||
| 3.1.2 | Performance Monitoring Baseline | R&C | ||||||
| 3.1.3 | Scrubbing Alerts | |||||||
| 3.1.4 | Dynamic SLAs | |||||||
| 3.1.5 | Timely Credit Determination and the Application of Credits | |||||||
| 3.1.6 | Scrubbing Alerts Production Implementation | |||||||
| SECTION 4.0 | Financial Consequences for Non-Performance | 0 | st | - | - | - | - | - |
| 4.1 | Withholding Payment or Other Remedies | R&C | - | - | - | - | - | |
| SECTION 5.0 | Migration and Transition Planning (Support Services) | 750 | st | - | - | - | - | - |
| 5.1 | Migration from MFN2 to MFN-3 | 750 | st | - | - | - | - | - |
| 5.1.1 | MFN-3 Core Services Readiness Plan | |||||||
| 5.1.2 | Migration Plan – Sites and Services | |||||||
| 5.1.3 | Migration - Staffing Resource Requirements | |||||||
| 5.1.4 | Migration - Knowledge Transfer | |||||||
| 5.1.5 | Migration - Project Management Tasks and Related Deliverables | |||||||
| 5.1.6 | Migration - Engineering Review | |||||||
| 5.1.7 | Migration - Provision Planning | |||||||
| 5.1.8 | Migration - Network Operations Center | |||||||
| 5.1.9 | Migration - Administrative Services | |||||||
| 5.1.10 | Migration - Payment Strategy Connection-By-Connection | R&C | ||||||
| 5.1.11 | Migration - Connection Testing Period with Fall Back Option | R&C | ||||||
| 5.2 | Transition between MFN-2 and the Successor Contract | NR | - | - | - | - | - | |
| Technical Evaluation | Technical Evaluation | 3,000.00 | st | - | - | - | - | - |
Evaluator's Name
Date
File details come from the government source that posted it. Updated .