A grid dispatch network answers to a different clock than an office network: a relay-protection packet that arrives late is operationally the same as one that never arrived, and the security regulation that governs it will not accept a flat network as an answer. We design the IP backbone that carries dispatch automation, comprehensive data and video on one physically hard-sliced infrastructure — SRv6 with FlexE hard pipes keeping each plane isolated on shared fibre, dual-plane reliability so a single failure cannot take down both, and sub-millisecond protection switching where relay traffic needs it. This is the grid's own production and dispatch backbone — distinct from the utility's office campus network (see Energy & Utility Campus Network): that page covers the workplace, this one covers the wires that keep the grid itself coordinated. Sized honestly for a municipal grid, a provincial grid or a cross-provincial backbone.
Four realities we design around on every grid backbone project:
One backbone, several hard-isolated planes, and a protection-switching budget measured in milliseconds:
Architecture drawn by AtlasCommTech following carrier-grade design practice. Diagram labels are kept in English for engineering clarity.
Why us: our founder spent 13 years inside the Huawei partner ecosystem delivering carrier networks — the same SRv6 and hard-slicing design discipline a dispatch backbone needs, not adapted from an office template. Our own Atlas industrial switches are built for exactly this substation yard: rated for roughly −40 to +85 °C, DIN-rail mounted and hardened to IEC 61850-3 class immunity — a solid fit for substation access, while the backbone routing core stays open to whichever brand suits your regulator, your budget and your team.
The solution is sized to your requirements and budget first — the same architecture can be delivered on several vendors' product lines. We help you choose by supply availability in your destination country, budget and your team's operating habits.
Six things a properly engineered dispatch backbone does that a generic WAN never will:
Tell us how many substations, how many dispatch sites and what your protection-service list looks like — the tier tells you the shape of the network:
| Scale tier | Typical site | What the design includes |
|---|---|---|
| Municipal / prefecture grid | One city or prefecture bureau · a handful of substations · one dispatch centre | A backbone ring of core/aggregation routers linking the dispatch centre to each substation, SRv6 with FlexE hard slicing for dispatch and comprehensive-data planes, sub-millisecond protection switching on the segments carrying relay traffic, substation-hardened access equipment throughout. |
| Provincial grid | A province-wide grid · multiple prefecture dispatch centres · one provincial control centre | A provincial backbone interconnecting prefecture rings, SDN-based centralized management with BGP-LS topology collection, dedicated capacity planned for new-energy interconnection growth, and dispatch/integrated-plane separation enforced end-to-end rather than city by city. |
| Cross-provincial backbone | Backbone linking multiple provincial grids or a regional transmission operator | A high-capacity SRv6 backbone across provincial boundaries, coordinated protection-switching design across the full path, standardized zoning and naming so each province's segment is a copy of the same design, and a staged rollout aligned to each provincial dispatch centre's own maintenance windows. |
The solution is built from these equipment categories — the brand is chosen with you at design stage. Exact models depend on your bandwidth, port counts, protection-service list and country — so we spec models after your requirements list, not before.
| Role | What it does |
|---|---|
| Core / backbone routers | Carry the SRv6 backbone and the FlexE hard slices between dispatch centres and aggregation points — the layer sized against your bandwidth and new-energy growth plan. |
| Aggregation / PE routers | Collect substation and site traffic and hand it into the correct hard slice on the backbone — the layer where the dispatch/integrated-plane split is enforced. |
| Substation access routers/switches (hardened) | Live in the substation yard, rated for the temperature range, EMC and vibration a comms-room switch was never built for. Terminate relay protection, automation and video traffic locally. |
| Dispatch-network boundary security gateway | The single controlled crossing point where the dispatch/protection plane may exchange only explicit, named traffic with the integrated or enterprise side — everything else is refused by design, matching electric power monitoring system security requirements. |
| Clock / time-synchronization devices | Deliver the precision timing that relay protection and dispatch automation depend on — a requirement most enterprise WAN designs never have to think about. |
| SDN controller / network management platform | Centralized topology, configuration and fault visibility across the whole backbone — BGP-LS and telemetry feed a live map instead of per-site logs. |
Send us your substation list, protection-service list, bandwidth forecast and new-energy interconnection queue — and the model list follows. That order keeps the design honest.
An engineer replies with a hard-sliced dispatch backbone design and the equipment-category list. Send us your requirements list — the model list follows.