Keep the right
connections working.
Wired, wireless and wide-area networks designed around service priorities, clear boundaries and recovery.
See the approachSwipe or use arrow keys to explore the diagram.
Read the diagram explanation
The work needs a permitted, usable connection.
Carries the required traffic.
Test routing, policy and capacity before relying on it.
Account for each path’s physical route, capacity and permitted traffic. An available link alone does not prove the application works.
Swipe or use arrow keys to explore the diagram.
Read the diagram explanation
The work needs a permitted, usable connection.
Unavailable in this scenario.
A usable alternate must be verified.
This example assumes a usable alternate. Verify routing, policy, capacity and the application session when the primary path fails.
Swipe or use arrow keys to explore the diagram.
Read the diagram explanation
The work needs a permitted, usable connection.
Unavailable in this scenario.
Also unavailable through shared power.
If both paths lose the same power supply, adding a link has not removed that dependency. Check the physical failure boundaries.
A route is only useful
if it holds under pressure.
Work through congestion, a failed connection and planned maintenance. Know what the service will do before the network changes.
Design around the physical environment
Survey coverage, model radio conditions and account for buildings, machinery and movement.
Separate traffic with a purpose
Align network zones and permitted routes to operational roles and service dependencies.
Test the difficult conditions
Validate path selection, application reachability and failure behaviour with the people who operate the service.
Part of the same system.
Connect the design decisions across these areas.
What needs to work better?
Start with the environment, the constraint and the change you need to make.
