CCDE Enterprise Case Study Part 10: Fully Managed vs Self-Managed SD-WAN Design Analysis

CCDE Enterprise Case Study Part 10 – Fully Managed vs Self-Managed SD-WAN Analysis

In this section of the CCDE enterprise case study, Jacobs is evaluating one of the most important strategic decisions in enterprise WAN transformation:

🎯 Should the SD-WAN solution be Fully Managed by a Service Provider or Self-Managed Internally?

This is not merely a technical discussion.

It is a:

• Business decision
• Operational decision
• Security decision
• Financial decision
• Architectural decision

From a CCDE perspective, this question tests:

• Operational architecture understanding
• Enterprise governance
• Provider relationships
• Scalability thinking
• Risk management

Table of Contents

• 1. Business Context
• 2. What Is Fully Managed SD-WAN?
• 3. What Is Self-Managed SD-WAN?
• 4. Complete Decision Matrix
• 5. Deep Analysis of Each Function
• 6. Enterprise Operational Mathematics
• 7. Automation and Machine Learning
• 8. SD-WAN Policy Examples
• 9. Key CCDE Takeaways
• 10. Related Articles

1. Business Context

Jacobs currently operates:

• 203 Jacobs stores
• 78 Toolmate stores
• 102 independent stores

This creates:

$$ 383\\ Total\\ Enterprise\\ Sites $$

Managing SD-WAN at this scale introduces enormous operational complexity.

Operational Complexity Formula

$$ Complexity \propto Sites \times Policies \times Providers $$

The company is also experiencing:

• Firewall scalability issues
• Slow change management
• Operational overhead
• Cloud migration challenges
• SaaS performance problems

2. What Is Fully Managed SD-WAN?

In a fully managed SD-WAN model:

• The provider manages deployment
• The provider manages circuits
• The provider manages overlays
• The provider manages monitoring
• The provider handles operational support

This creates:

$$ Operational\\ Outsourcing $$

Advantages

• Faster deployment
• Reduced staffing burden
• 24x7 provider operations
• Large operational scale
• Integrated provider tooling

Disadvantages

• Reduced flexibility
• Reduced direct control
• Longer policy change cycles
• Provider dependency
• SLA restrictions

3. What Is Self-Managed SD-WAN?

In a self-managed model:

• Jacobs controls policies
• Jacobs controls operations
• Jacobs manages overlays
• Jacobs handles integrations
• Jacobs maintains governance

Advantages

• Complete flexibility
• Faster internal changes
• Application-level optimization
• Better business alignment
• Enhanced visibility

Disadvantages

• Requires skilled staff
• Operational burden increases
• Monitoring complexity increases
• Higher staffing requirements

4. Complete Decision Matrix

Function Topic	Optimal Choice
Application-aware routing policies and QoS	Self-Managed
Speed of deployment	Fully Managed
Flexibility	Self-Managed
Ease of integrations	Self-Managed
Geographical coverage	Fully Managed
Control over network and data	Self-Managed
Skills and staffing	Fully Managed
Infrastructure and circuit procurement	Fully Managed
Underlay and overlay monitoring	Fully Managed

5. Deep Analysis of Each Function

Application-Aware Routing Policies and QoS

✅ Best Choice: Self-Managed

Jacobs understands:

• Its own applications
• Voice requirements
• ERP behavior
• Jaystore application sensitivity
• Cloud application priorities

The provider does not understand business application flows at the same depth.

$$ Application\\ Performance = Routing + QoS + Business\\ Context $$

Relevant QoS and MPLS concepts:

• Understanding QoS Congestion Management
• Complete Guide to BGP Local Preference

Speed of Deployment

✅ Best Choice: Fully Managed

Service providers already have:

• Carrier relationships
• Field engineers
• Regional deployment capability
• Operational frameworks

At 383 sites, deployment speed becomes a massive operational factor.

$$ Deployment\\ Time \propto Sites \times Logistics $$

Flexibility

✅ Best Choice: Self-Managed

Self-managed SD-WAN provides:

• Rapid policy changes
• Custom integrations
• Fast experimentation
• Business agility

Provider-managed environments usually introduce:

• Change windows
• Approval delays
• SLA constraints
• Operational rigidity

Ease of Integrations

✅ Best Choice: Self-Managed

Jacobs understands:

• Its DC architecture
• Security policies
• Application dependencies
• Migration strategy

This is especially important because:

• Toolmate systems are partially integrated
• Independent stores remain isolated
• Firewall dependencies exist

Geographical Coverage

✅ Best Choice: Fully Managed

Providers typically have:

• Regional engineers
• Field logistics
• Nationwide infrastructure
• Rapid replacement capability

This matters greatly for:

$$ Distributed\\ Retail\\ Enterprises $$

Control Over Network and Data

✅ Best Choice: Self-Managed

Enterprises usually prefer direct control over:

• Traffic visibility
• Security policies
• Application flows
• Sensitive business data

Skills and Staffing

✅ Best Choice: Fully Managed

Service providers specialize in:

• WAN operations
• Monitoring
• Incident response
• Carrier escalation

Their core business is:

$$ Network\\ Operations $$

Infrastructure and Circuit Procurement

✅ Best Choice: Fully Managed

Providers benefit from:

• Economies of scale
• Bulk purchasing power
• Carrier relationships
• Supply chain efficiencies

Underlay and Overlay Monitoring

✅ Best Choice: Fully Managed

Modern SD-WAN environments generate massive telemetry.

$$ Telemetry = Sites \times Flows \times Metrics $$

Providers often have:

• NOCs
• SIEM platforms
• AI analytics
• Dedicated monitoring systems

6. Enterprise Operational Mathematics

Operational Cost Formula

$$ Operational\\ Cost = Staff + Tooling + Circuits + Support $$

Provider Efficiency Formula

$$ Efficiency \propto Scale $$

Flexibility Formula

$$ Flexibility \propto Administrative\\ Control $$

Risk Formula

$$ Risk = Complexity - Governance $$

7. Automation and Machine Learning

Modern SD-WAN platforms increasingly rely on:

• AI-driven path selection
• Anomaly detection
• Predictive analytics
• Traffic forecasting

Machine learning concepts relevant to SD-WAN analytics:

• Time Series Forecasting Beginners Guide
• How to Evaluate and Ensure Your Data
• Stationary vs Nonstationary Data

8. SD-WAN Policy Examples

Example – Application-Aware Routing

policy
 app-route-policy OFFICE365

policy

 app-route-policy OFFICE365

  sequence 10

   match application office365

   action accept

    set local-tloc-color biz-internet

Example – SLA Policy

sla-class VOICE

sla-class VOICE

 latency 100

 jitter 20

 loss 1

Why Application-Aware Routing Matters

Applications have different requirements:

• Voice requires low latency
• ERP requires stability
• SaaS requires Internet optimization
• Backup traffic tolerates delay

This is why:

$$ Intent\\ Based\\ Routing $$

is one of the biggest advantages of SD-WAN.

9. Key CCDE Takeaways

🎯 Core Architectural Lesson

Fully managed SD-WAN optimizes:

• Scale
• Deployment
• Operations
• Monitoring

Self-managed SD-WAN optimizes:

• Flexibility
• Control
• Business alignment
• Application optimization

There is no universally correct answer.

The optimal architecture depends on:

• Business priorities
• Operational maturity
• Internal skills
• Risk appetite
• Budget

10. Related Articles

CCDE Enterprise Case Study Series

• CCDE Enterprise Case Study Part 1 – Enterprise Architecture
• CCDE Enterprise Case Study Part 2 – Main Enterprise Issues
• CCDE Enterprise Case Study Part 3 – Scalability Analysis
• CCDE Enterprise Case Study Part 4 – MPLS Analysis
• CCDE Enterprise Case Study Part 5 – MPLS Operational Design
• CCDE Enterprise Case Study Part 6 – DMVPN Architecture
• CCDE Enterprise Case Study Part 7 – Enterprise Design Decisions
• CCDE Enterprise Case Study Part 8 – SD-WAN Security
• CCDE Enterprise Case Study Part 9 – Direct Internet Access Security
• CCDE Enterprise Case Study Part 11: Self-Managed vs Managed SD-WAN Architecture

Related Enterprise Networking Concepts

• Complete Guide to BGP Local Preference
• Understanding QoS Congestion Management
• Reliable BGP Peering Physical Connectivity
• Optimizing OSPF Timers for Faster Convergence

Final Conclusion

This CCDE scenario demonstrates a key enterprise architecture reality:

SD-WAN is not simply a networking project.

It is:

• An operational transformation
• A governance transformation
• A tooling transformation
• A staffing transformation
• A business transformation

Jacobs must balance:

$$ Control \leftrightarrow Operational\\ Simplicity $$

The most likely real-world enterprise outcome would actually be:

A Co-Managed Hybrid SD-WAN Model

where:

• The provider manages infrastructure and monitoring
• Jacobs controls policies and application routing

This is increasingly common in large enterprise WAN architectures.