Multi-site enterprises
Branch connectivity that has to behave the same way at every location.
Managed services · Meraki SD-WAN
Branch connectivity, run to a service level.
Cloud-managed branch connectivity and application-aware networking for distributed enterprises using Meraki MX and virtual MX.
How the service runs
Concept model
- 01 · Onboard Map sites, links and policy Inventory · templates · access
- 02 · Operate Run WAN day to day Auto VPN · links · changes
- 03 · Assure Report on availability and apps Analytics · SLA · lifecycle
A conceptual service lifecycle used to explain the model—not a customer deployment.
Overview
What it is
Cloud-managed branch connectivity and application-aware networking, operated by CDS. The service is designed to simplify connectivity management while improving branch availability, WAN visibility, application performance and operational control.
- 01
MX and vMX dashboard operations
- 02
Auto VPN and site-to-site VPN management
- 03
WAN link monitoring, alerting and reporting
- 04
Application prioritisation and segmentation policy
Service inclusions
What is included
Supported Meraki platforms: Meraki MX security appliances, virtual MX (vMX) instances and the associated Meraki licensing.
| Service inclusion | Managed Meraki SD-WAN |
|---|---|
| Meraki MX / vMX dashboard operations | Included |
| Auto VPN and site-to-site VPN management | Included |
| WAN link monitoring and alerts | Included |
| 24x7 network monitoring | Optional / Tiered |
| Configuration management | Included |
| Firmware and software lifecycle | Included |
| Reporting and analytics | Included |
| License and subscription tracking | Included |
| Application prioritization | Included |
| WAN and cloud connectivity optimization | Included |
| Network segmentation policy support | Included |
| Security and connectivity policy management | Included |
| API / ITSM integration | Optional |
| Complex IMACD / migration projects | Add-on |
Read the qualifiers. Rows marked optional, tiered, add-on, licence-dependent or “as per SLA” are not included by default — each is confirmed during scoping and written into the service agreement.
Right fit
Who it is for
Cloud-weighted traffic
Application performance to SaaS and cloud platforms matters as much as site-to-site.
Small WAN teams
Link health, policy and firmware lifecycle need an owner with defined hours.
Outcomes
What you get
Availability
WAN link monitoring and alerting as a standing service output.
Performance
Application prioritisation and connectivity optimisation applied under change control.
Control
Configuration, firmware and policy managed centrally rather than per site.
Evidence
Reporting and analytics that show what the WAN actually did.
Questions, answered directly
What buyers usually need to establish
Is 24x7 monitoring part of this service?+
No. 24x7 network monitoring is listed as optional and tiered. Standard coverage follows the contracted service level; 24x7 with dedicated escalation governance is an add-on.
Can CDS integrate with our ITSM tooling?+
API and ITSM integration is available as an option rather than a default inclusion, and is scoped separately.
Are migrations included?+
No. Complex IMACD and migration projects are add-ons. Standard changes are covered by the recurring service.
Start with who runs it today.
Describe the current estate, the operating gaps and the service level the business expects. Scope and packaging follow that conversation.