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 TEM, DIA and MPLS

Requirements, questions, and evaluation criteria specific to TEM, DIA and MPLS procurement

7 min read

RFPs are critical when procuring TEM, DIA, and MPLS solutions due to the complex interplay of network architecture, performance requirements, and cost considerations. A well-structured RFP ensures alignment between business needs and the technical capabilities offered by various providers in this evolving landscape.

What makes TEM, DIA and MPLS RFPs different

TEM, DIA, and MPLS RFPs are unique because they require a deep understanding of network topology, bandwidth requirements, and application performance needs. Unlike generic software RFPs, these involve intricate details regarding service level agreements (SLAs), latency guarantees, and redundancy mechanisms. The shift towards hybrid networks, combining MPLS for sensitive data and DIA for cloud-bound traffic, adds another layer of complexity.

Organizations must carefully evaluate vendors" ability to manage this hybrid environment and ensure seamless integration with existing infrastructure.nnFurthermore, geographical considerations and regulatory compliance play a significant role. Different regions have varying infrastructure availability and pricing models, impacting the overall cost and performance of the network.

Compliance standards like GDPR in Europe or specific industry regulations require careful consideration of data privacy and security protocols. The RFP must address these regional and compliance factors to ensure the chosen solution meets all necessary requirements.nnFinally, the long-term nature of network contracts (often 3-5 years) necessitates a thorough evaluation of vendors" financial stability, support capabilities, and future roadmap.

The RFP should include questions about their investment in emerging technologies like AI-driven automation and their ability to adapt to evolving business needs.

  • Bandwidth requirements and scalability for future growth
  • Service Level Agreements (SLAs) for uptime, latency, and jitter
  • Security protocols and compliance certifications
  • Integration with existing network infrastructure and SD-WAN solutions

RFP vs RFI vs RFQ

Here's when to use each document type when procuring TEM, DIA and MPLS 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 TEM, DIA, and MPLS procurements, an RFI is useful for initial market exploration and understanding vendor capabilities. An RFP is essential for detailed technical and commercial evaluation, while an RFQ is less suitable due to the complexity and customization involved in network solutions.

Technical requirements checklist

Use this checklist when defining your RFP scope.

Connectivity Requirements

  • MPLS bandwidth requirements per site
  • DIA bandwidth requirements per site
  • Redundancy and failover requirements
  • Geographic coverage requirements
  • Latency and jitter requirements

Security Requirements

  • Firewall requirements
  • VPN requirements
  • Encryption requirements
  • Compliance requirements (e.g., PCI-DSS, HIPAA)
  • Threat detection and prevention capabilities

Management and Monitoring

  • Real-time network monitoring capabilities
  • Reporting and analytics capabilities
  • Alerting and notification capabilities
  • Centralized management platform
  • Integration with existing monitoring tools

Service Level Agreements (SLAs)

  • Uptime guarantee
  • Latency guarantee
  • Jitter guarantee
  • Packet loss guarantee
  • Mean Time To Repair (MTTR)

SD-WAN Integration

  • Compatibility with existing SD-WAN solution
  • Application-aware routing capabilities
  • Dynamic bandwidth allocation
  • Centralized policy management
  • Zero-touch provisioning

Questions to include in your RFP

Network Architecture

  • Describe your network architecture and how it supports MPLS and DIA services.
    Understanding the underlying architecture is critical for assessing scalability and reliability.
  • How do you ensure network redundancy and failover in case of outages?
    Redundancy is crucial for maintaining business continuity.
  • What are your peering arrangements and how do they impact network performance?
    Peering arrangements affect latency and overall network speed.
  • How does your solution support a hybrid WAN environment?
    Many organizations are moving to a hybrid approach, blending MPLS and DIA.

Service Level Agreements (SLAs)

  • What are your standard SLAs for uptime, latency, jitter, and packet loss?
    SLAs define the guaranteed level of service.
  • What are the penalties for failing to meet SLA targets?
    Penalties provide recourse if service levels are not met.
  • How do you monitor and report on SLA performance?
    Monitoring and reporting are essential for tracking performance against SLAs.
  • Can you provide customized SLAs to meet our specific requirements?
    Customized SLAs ensure alignment with unique business needs.

Security

  • Describe your security measures to protect against network threats.
    Security is paramount for protecting sensitive data.
  • What compliance certifications do you hold (e.g., PCI-DSS, HIPAA)?
    Certifications demonstrate adherence to industry standards.
  • How do you handle data encryption and access control?
    Encryption and access control are vital for data privacy.
  • Do you offer managed security services, such as firewall management and intrusion detection?
    Managed security services can reduce the burden on internal IT teams.

Management and Monitoring

  • What network management and monitoring tools do you provide?
    Management tools are essential for proactive issue resolution.
  • Can you provide real-time visibility into network performance and traffic patterns?
    Real-time visibility enables quick identification of bottlenecks.
  • Do you offer a centralized management portal for all services?
    A centralized portal simplifies network administration.
  • How do you integrate with existing monitoring tools?
    Integration avoids the need for separate monitoring systems.

Pricing and Licensing

  • Provide a detailed breakdown of your pricing model for MPLS and DIA services.
    Transparency in pricing is crucial for accurate budgeting.
  • Are there any hidden costs or fees?
    Hidden costs can significantly impact the total cost of ownership.
  • What are your contract terms and early termination fees?
    Understanding contract terms and fees is essential for long-term planning.
  • Do you offer volume discounts or other incentives?
    Volume discounts can reduce overall costs.
  • What are the payment terms?
    Payment terms affect cash flow.

Implementation and Support

  • Describe your implementation process and timeline.
    A clear implementation plan minimizes disruption.
  • What level of support do you provide during and after implementation?
    Reliable support is crucial for resolving issues quickly.
  • What is your process for handling service requests and incidents?
    A well-defined process ensures efficient issue resolution.
  • Do you offer training for our IT staff?
    Training enables internal teams to manage the network effectively.

Future Roadmap

  • What is your roadmap for future technology enhancements and service offerings?
    Understanding the vendor's vision ensures long-term compatibility.
  • How do you plan to incorporate emerging technologies like AI and automation into your network services?
    AI and automation can improve network efficiency and resilience.
  • How do you adapt to changing business needs and market trends?
    Adaptability is crucial for staying ahead of the curve.
  • What are your plans for expanding your network infrastructure and geographic coverage?
    Expansion plans ensure continued support for growing businesses.

Compliance and security requirements

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

PCI-DSS

Required if handling payment card data. If applicable, request current PCI-DSS compliance certificate and AOC

HIPAA

Required for healthcare data. If applicable, request BAA template and HIPAA compliance documentation

SOC 2 Type II

Required for data security and availability. If applicable, request SOC 2 Type II report

GDPR

Required for handling eu citizen data. If applicable, request GDPR compliance documentation and data processing agreement

ISO 27001

Required for information security management. If applicable, request ISO 27001 certification

Evaluation criteria

Here is the suggested weighting for TEM, DIA and MPLS RFPs.

Functionality Fit How well the solution meets stated requirements
25%
Service Level Agreements (SLAs) Guaranteed uptime, latency, and jitter performance
20%
Security Security measures and compliance certifications
15%
Total Cost of Ownership Implementation, licensing, and ongoing costs
15%
Management and Monitoring Capabilities Ease of management and real-time visibility
10%
SD-WAN Integration Compatibility with existing SD-WAN solution
10%
Vendor Reputation and Experience Track record and customer references
5%

Some weights were adjusted based on your priorities.

  • Increase if replacing a highly customized legacy system

Red flags to watch

  • Vague pricing responses

    Vendors who can't provide clear pricing often have hidden costs or complex fee structures that inflate TCO

  • No customer references in your industry

    Lack of relevant references suggests limited experience with your specific requirements and use cases

  • Inadequate SLA guarantees

    Weak SLAs signal a lack of confidence in their ability to deliver consistent performance

  • Poor communication and responsiveness

    Difficulties in communication during the sales process often translate to poor support after implementation

  • Lack of compliance certifications

    Missing certifications indicate a failure to meet industry standards for security and data privacy

Key metrics to request

Ask vendors to provide benchmarks from similar customers.

Implementation timeline for similar customers

Helps set realistic expectations and identify potential delays

Average time to first value

Indicates how quickly you'll see ROI from the investment

Network uptime percentage

Measures the reliability of the network service

Average latency and jitter

Impacts application performance and user experience

Number of security incidents

Indicates the effectiveness of security measures