A reference architecture is a set of design decisions made explicit, and the interesting parts are usually the consequences the authors chose to name. Data center, campus, WAN, cloud, and edge each run on their own platforms, often from different vendors, and the architecture takes that fragmentation as its starting point rather than a problem to wish away.
Gartner® says, “These converging pressures are driving a shift toward modular enterprise network architectures that can adapt to dynamic requirements and avoid vendor lock-in.”
The brief lays the network out as loosely coupled, per-domain building blocks, each procured on its own merits and joined through open standards. Build it that way on purpose, and you create a gap on purpose too, which is why the architecture answers with a dedicated operations layer that runs across every block.
Where Selector is named
Selector is named in the Reference Architecture Brief as an example technology within the NetOps Platforms and Tools layer, listed under network observability and performance monitoring, and under digital twin.
We believe Selector appears in this layer because of where our work sits: collecting and correlating telemetry across domains and vendors into a single, queryable view of network and service health. That correlation layer is Selector’s reason for being.
The layer the architecture adds, and why
Building the network as per-domain blocks is the right call for flexibility and procurement leverage. The trade is that each domain’s native tooling sees its own block clearly and very little past it. The reference architecture resolves that with a NetOps platform layer whose entire job is to view across the blocks.
Gartner says : “These platforms extend beyond vendor-native capabilities, providing cross-domain insights and control that native tools typically cannot achieve.”
A campus controller manages the campus well. A fabric manager manages the data center well. The picture that spans both, plus the WAN and cloud between them, has to be assembled by something built for that purpose.
According to Gartner, “These platforms collect, correlate, and normalize network and traffic data from multiple sources to provide a consistent and unified view of the network state.”
Correlation and normalization across heterogeneous sources is the hard engineering, and it is what makes everything above it trustworthy. Monitoring, analytics, anomaly detection, and any agent reasoning about the network all inherit the quality of that layer. Feed them disconnected per-domain data and each works in its own corner. Give them one normalized, correlated view and they operate on a shared understanding of what the network is actually doing. The more deliberately an organization splits its network into independent blocks, the more it needs a layer that reassembles them.
Notes for your own build
The brief is practical about the long-term role this layer can play. Gartner notes “you can leverage these platforms as your own ‘IT Infrastructure’ data lake and use it to perform data science tasks or feed your own large language models.” That reframes the correlated layer as durable infrastructure rather than a dashboard with a shelf life.
A few notes if you are designing toward this. Define your building blocks and their seams first, standardizing the integration points on open protocols such as BGP, REST API, SNMP, and streaming telemetry. Choose the cross-domain layer on the criteria that actually matter here, the breadth of sources it can ingest and the quality of its correlation across vendors, since strong per-domain coverage is not the thing you are missing. And treat the correlated data as foundational, because the same normalized layer that powers monitoring today is what your analytics and any future agents will reason over; build it to be queried and reused.
Modular architecture will keep spreading across enterprise networks. The organizations that get the most from it will invest early in the layer that puts a single, correlated view back together across every block, because everything downstream, from dashboards to analytics to agents, is standing on it.
Stay Connected
Selector is helping organizations move beyond legacy complexity toward clarity, intelligence, and control. Stay ahead of what’s next in observability and AI for network operations:
- Subscribe to our newsletter for the latest insights, product updates, and industry perspectives.
- Follow us on YouTube for demos, expert discussions, and event recaps.
- Connect with us on LinkedIn for thought leadership and community updates.
- Join the conversation on X for real-time commentary and product news.
Required disclosures
Gartner, Reference Architecture Brief: Next-Generation Enterprise Networks, Jorge Aragon, 20 April 2026.
GARTNER is a trademark of Gartner, Inc. and/or its affiliates.
Gartner does not endorse any company, vendor, product or service depicted in its publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner publications consist of the opinions of Gartner’s business and technology insights organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this publication, including any warranties of merchantability or fitness for a particular purpose.
