Skip to main content

Permissions

Add user
Done

Start your AI search

AI search
Outbound call compliance Gamification for customer service Outsourcing services

How to write an RFP for dedicated fiber

Requirements, questions, and evaluation criteria specific to dedicated fiber procurement

7 min read

Procuring dedicated fiber is a high-stakes decision that goes beyond simple bandwidth considerations. Unlike software, it involves physical infrastructure and long-term commitments, making a well-structured RFP crucial for ensuring network reliability and avoiding costly delays.

What makes dedicated fiber RFPs different

Dedicated fiber RFPs are unique due to the blend of technical specifications, civil engineering dependencies, and service level agreements. Unlike cloud-based solutions, dedicated fiber involves physical construction and route planning, requiring careful evaluation of the provider's infrastructure and local expertise. The RFP must address not only bandwidth and latency but also redundancy, path diversity, and the provider's ability to navigate local permitting processes.

Furthermore, the long-term nature of fiber contracts necessitates a thorough assessment of the provider's financial stability and commitment to ongoing support.

  • Fiber route redundancy and diversity to minimize downtime
  • Provider's ownership of the 'last mile' fiber asset
  • Service Level Agreements (SLAs) covering uptime, latency, jitter, and packet loss
  • Provider's experience with local permitting and construction

RFP vs RFI vs RFQ

Here's when to use each document type when procuring dedicated fiber software.

RFI

Request for Information

Use early in your search to understand what vendors offer and narrow your list. Gather general capabilities, company background, and high-level pricing ranges.

RFP

Request for Proposal

Use when you know your requirements and want detailed vendor solutions and pricing. This is your main evaluation document for shortlisted vendors.

RFQ

Request for Quote

Use when requirements are fixed and you just need final pricing. Often used after RFP when you're ready to negotiate with finalists.

For dedicated fiber, an RFI is helpful for initial market research to understand available providers and their geographic reach. An RFP is essential for a detailed evaluation of technical capabilities, service level agreements, and implementation plans. An RFQ is generally not suitable due to the complexity and customized nature of dedicated fiber deployments.

Technical requirements checklist

Use this checklist when defining your RFP scope.

Bandwidth and Performance

  • Symmetrical bandwidth requirements (upload and download)
  • Minimum guaranteed bandwidth
  • Latency requirements (round-trip time)
  • Jitter tolerance
  • Packet loss rate

Network Redundancy and Diversity

  • Redundant fiber paths into the building
  • Geographically diverse routing
  • Automatic failover mechanisms
  • Backup power solutions
  • Redundant hardware

Service Level Agreements (SLAs)

  • Uptime guarantee
  • Latency guarantee
  • Jitter guarantee
  • Packet loss guarantee
  • Mean Time to Repair (MTTR)
  • SLA credits for breaches

Security Requirements

  • Physical security of fiber infrastructure
  • DDoS protection
  • Encryption options
  • Compliance with relevant security standards (e.g., SOC 2, HIPAA, PCI-DSS)
  • Vulnerability scanning and penetration testing

Implementation and Support

  • Project management methodology
  • Installation timeline
  • On-site support availability
  • 24/7 network monitoring
  • Escalation procedures

Questions to include in your RFP

Network Architecture and Infrastructure

  • Describe your network architecture, including the location of your Points of Presence (PoPs) and the routes your fiber takes to reach our location.
    Understanding the network topology helps assess potential points of failure and latency.
  • Do you own the physical fiber infrastructure in our area (the "last mile"), or do you lease it from a third party?
    Owning the fiber typically results in faster repair times and greater control over service quality.
  • What redundancy and diversity measures are in place to protect against fiber cuts or equipment failures?
    Redundancy ensures business continuity in case of network disruptions.
  • What is the physical path of the fiber entering our building, and are there alternative entry points available?
    Multiple entry points provide redundancy and protection against single points of failure.

Performance and Service Level Agreements

  • What are your guaranteed uptime, latency, jitter, and packet loss metrics, and what credits are offered if these metrics are not met?
    SLAs define the expected level of service and provide recourse for performance issues.
  • What tools do you use to monitor network performance and proactively identify potential issues?
    Proactive monitoring helps prevent outages and ensures consistent performance.
  • What is your documented Mean Time to Repair (MTTR) for fiber cuts in our specific ZIP code?
    MTTR indicates how quickly the provider can restore service in case of a physical outage.
  • Can you provide real-time network performance data and reporting through a customer portal?
    Transparency into network performance allows for proactive issue identification and resolution.

Implementation and Deployment

  • What is your standard implementation timeline, and what factors could cause delays?
    Understanding the implementation process helps set realistic expectations and avoid surprises.
  • What permits are required for installation, and who is responsible for obtaining them?
    Permitting delays are a common cause of implementation delays.
  • What are the requirements for building access and internal cabling?
    Clear communication of requirements ensures a smooth installation process.
  • Do you provide project management services to oversee the implementation process?
    Dedicated project management ensures accountability and coordination.

Security

  • What security measures are in place to protect our data in transit?
    Protecting data is paramount.
  • Do you offer DDoS protection services?
    DDoS attacks can disrupt network connectivity and impact business operations.
  • Are you compliant with relevant security standards, such as SOC 2, HIPAA, or PCI-DSS?
    Compliance demonstrates a commitment to security best practices.
  • What is your process for responding to security incidents?
    A well-defined incident response plan minimizes the impact of security breaches.

Pricing and Contract Terms

  • Provide a detailed breakdown of all recurring and non-recurring costs, including installation fees, monthly service charges, and any usage-based fees.
    Transparency in pricing is essential for accurate budgeting.
  • What are the contract term options, and what are the penalties for early termination?
    Understanding contract terms helps avoid unexpected costs.
  • Are there any volume discounts or other incentives available?
    Volume discounts can reduce the overall cost of the service.
  • What are the escalation procedures for price increases?
    Understanding price escalation policies helps anticipate future costs.

Support and Maintenance

  • What are your support hours, and what methods of support are available (phone, email, online portal)?
    Reliable support is crucial for resolving issues quickly.
  • Do you provide a dedicated account manager?
    A dedicated account manager provides a single point of contact for all inquiries.
  • What is your escalation process for critical issues?
    A clear escalation process ensures timely resolution of urgent problems.
  • Do you have a Network Operations Center (NOC) that operates 24/7/365?
    A 24/7 NOC ensures continuous monitoring and support.

Compliance and security requirements

Depending on your industry, you may need to require proof of these certifications and standards.

SOC 2 Type II

Required for organizations requiring assurance of data security and availability. If applicable, request a copy of the vendor's most recent SOC 2 Type II report.

HIPAA

Required if handling protected health information (phi). If applicable, request a Business Associate Agreement (BAA) and documentation of HIPAA compliance measures.

PCI-DSS

Required if processing credit card payments. If applicable, request a copy of the vendor's PCI-DSS compliance certificate and Attestation of Compliance (AOC).

FISMA

Required for us federal government agencies and contractors. If applicable, request documentation of FISMA compliance and security controls.

Evaluation criteria

Here is the suggested weighting for dedicated fiber RFPs.

Network Performance (Latency, Jitter, Packet Loss) Evaluates the provider's ability to deliver consistent and reliable network performance.
25%
Redundancy and Availability Assesses the provider's infrastructure and procedures for ensuring high availability and minimizing downtime.
20%
Service Level Agreement (SLA) Evaluates the comprehensiveness and enforceability of the provider's SLA.
15%
Implementation Plan and Timeline Assesses the feasibility and efficiency of the provider's proposed implementation plan.
10%
Security Measures Evaluates the provider's security controls and compliance with relevant standards.
10%
Pricing and Total Cost of Ownership (TCO) Compares the overall cost of the solution, including installation, recurring fees, and potential hidden costs.
10%
Customer Support and Responsiveness Evaluates the provider's ability to provide timely and effective support.
10%

Red flags to watch

  • Unwillingness to provide detailed network diagrams

    This suggests a lack of transparency and potential hidden vulnerabilities in their network.

  • Vague or incomplete SLA terms

    This indicates a lack of commitment to service quality and difficulty in holding the provider accountable.

  • Lack of experience with similar deployments

    This suggests a higher risk of implementation delays and unexpected challenges.

  • Aggressive pricing that seems too good to be true

    This may indicate hidden costs or a compromise in service quality.

  • Inability to provide references from existing customers

    This raises concerns about the provider's track record and customer satisfaction.

Key metrics to request

Ask vendors to provide benchmarks from similar customers.

Average latency to key cloud providers (e.g., AWS, Azure)

Lower latency improves application performance and user experience.

Network uptime over the past 12 months

Historical uptime data provides insights into the provider's reliability.

Mean Time to Repair (MTTR) for fiber cuts

MTTR indicates how quickly the provider can restore service in case of an outage.

Percentage of support calls resolved on the first contact

First-call resolution rate reflects the efficiency and effectiveness of the provider's support team.

Customer satisfaction scores

Customer satisfaction scores provide insights into the overall quality of the provider's service.