Access and edge
Owner named in the service schedule
- Carrier access
- Customer edge
- Licences
Managed networks
A network operating model built for change
Bring connectivity, routing, application policy, monitoring and service ownership into one controlled design across sites, users and cloud environments.
One design brings together
We map first Every network
- Applications that matter
- Where users and workloads sit
- Paths available at each site
- Behaviour in congestion or failure
Start with applications and policy
Decide how traffic should behave before choosing a platform
Start by mapping the applications that matter and where your users and workloads sit. Then look at which paths are available and how traffic should behave when a link is congested or fails.
SD-WAN can apply central policy across multiple links. Results still depend on the access services underneath, the configuration and the operating process.
Illustrative layers only. Your design names the actual platform, services and responsibilities.
- Applications and usersWhich applications matter and where people and workloads are
- PolicyHow traffic behaves during congestion or failure
- SD-WAN edgeApplies central policy across multiple links
- UnderlayThe access services every result depends onFoundation
Managed network scope
From design to day-to-day operation
Each stage has a defined scope, so it is clear what is designed, deployed, monitored and operated, and by whom.
- 01
Design
Topology, addressing, routing, segmentation, path policy, resilience, cloud access and operational acceptance.
- 02
Deploy
Equipment staging, site readiness, installation, configuration, migration, testing and documentation.
- 03
Monitor
Device, link, tunnel and application visibility supported by the selected platform and service.
- 04
Operate
Incident triage, carrier coordination, approved changes, configuration control, reporting and lifecycle review.
Migration
Migration without unnecessary disruption
Before each cutover, we account for addressing, routing, firewall rules, voice, local services, printers, operational technology and third-party access.
Discovery
Confirm sites, services and dependencies
Pilot
Prove the design at representative sites
Standard templates
Repeatable configuration for each site type
Site waves
Move sites in planned groups
Acceptance testing
Checks agreed before each cutover
Rollback
A way back if a cutover does not pass
Example sequence. Discovery determines whether current services can be kept in the target design.
Review my WANSecurity integration
Design how network and security controls work together
We define how network segmentation, firewalls, secure web access, identity, remote access and cloud security work together.
Where SASE or other security services are included, the proposal names the approved capability and who is responsible for each part.
SD-WAN alone is not a complete security solution.
Controls we design together
Each control is defined alongside the network, rather than added afterwards.
- Network segmentation
- Firewalls
- Secure web access
- Identity
- Remote access
- Cloud security
Visibility
Visibility that supports action
Dashboards should distinguish availability, utilisation, loss, latency, jitter, path changes and application experience where the platform supports those measures.
Reports need context and ownership, not just charts.
Measures kept distinct, where the platform supports them
- Availability
- Utilisation
- Loss
- Latency
- Jitter
- Path changes
- Application experience
Every report carries
- Context that explains what changed and why it matters
- An owner for each follow-up action
Responsibility
Define who owns each layer
The service schedule should state who is responsible for carrier access, customer edge, licences, configuration, monitoring, security policy, site LAN, Wi-Fi, incidents, changes and third-party dependencies.
Configuration and policy
Owner named in the service schedule
- Configuration
- Monitoring
- Security policy
Site and operations
Owner named in the service schedule
- Site LAN and Wi-Fi
- Incidents and changes
- Third-party dependencies
Grouping is illustrative. Your proposal and service schedule set the actual owner of each layer.
Map the operating modelQuestions
Frequently asked questions
Straight answers about SD-WAN, security and existing carriers.
Does SD-WAN replace internet or private connectivity?
No. SD-WAN uses underlying network services and applies policy across them. The quality, diversity and capacity of those services still matter.
Will SD-WAN improve every application?
Not automatically. It can select paths and apply policy within the platform’s capabilities. Application design, distance, cloud architecture, internet conditions and endpoint performance also affect what your users experience.
Is SD-WAN secure?
It depends. SD-WAN can provide encrypted tunnels, segmentation and policy features. Your complete security posture depends on architecture, configuration, identity, inspection, endpoint and operating controls.
Can we keep our existing carriers?
Possibly. Discovery determines whether your current services are suitable, contractually usable and operationally supportable in the target design.
Related services
The network connects everything else
A managed network depends on the access underneath it and carries the cloud, voice and support services on top of it.
-
Enterprise Connectivity
Enterprise fibre, NBN pathways, business broadband, fixed wireless, mobile, satellite, private networks and cloud connectivity, subject to location and catalogue.
Explore -
Cloud and Data Centre
Assessment, migration, connectivity, backup, disaster recovery, hosting, colocation and managed cloud pathways.
Explore -
Voice and Unified Communications
SIP, hosted voice, numbers, cloud calling, contact workflows and authorised collaboration integrations.
Explore -
Service Management
Onboarding, incidents, changes, reporting, renewals, supplier coordination and transition.
Explore
Network workshop
Talk through your network before you change it
Tell us about your sites, current access services, critical applications and the issues you want to solve. We’ll identify what discovery is needed and where SD-WAN or a managed network fits.
Helpful to have ready
- Number of locations and principal site types
- Current access providers and technologies, if known
- Critical SaaS, cloud, voice, video, data-centre and operational applications
- Current issues: visibility, performance, failover, change control, security integration, cost or end-of-life equipment
- How you want it run: internal IT, managed service, co-managed or not yet decided
Do not include credentials, IP addressing or detailed network configurations.
Already a customer?
Use the contact path in your service schedule for eligible priority incidents.