PlatformProduct

NetTopo

One end-to-end view, stitched from everything you already have

Loads topology, inventory and configuration data across the entire network — bulk auto-load and discovery of all network elements across multiple domains, vendors and technologies, ingesting JSON, XML, MML, CSV, XLS and YANG. It gives users a digital map charting every node, link and connection, with no need for pre-defined data models.

84B → 35M
FTTH permutations reduced by line-of-sight filtering
120k / 1.4M
NAPs and ports loaded in one fibre programme

What we can evidence

Measured
84B → 35M
Permutations narrowed by line-of-sight

Compute genuine fibre reachability instead of checking the nearest few access points.

Across roughly 120,000 NAPs carrying 1.4 million ports and 730,000 subscribers, all 84 billion customer-to-port permutations were evaluated, then narrowed by line-of-sight within 500 metres to about 35 million viable combinations, with a unique port pre-allocated per customer.

The problem it solves

Operators typically run multiple, disconnected sources of truth — separate views for facility management, asset management, service assurance and service provisioning that do not agree with each other. NetTopo consolidates these into a single source spanning RAN, Core, OLT, IP, DWDM and microwave.

  • IP vs VLAN vs physical mismatches — IP stitching is not always possible because Layer 2 switching is mostly used.
  • Weak processes — data is often captured after the event, in the office, on spreadsheets, with little database integration.
  • Data integrity — manual, infrequent data based on filtered extracts and reports.
  • Data availability — limited access to network elements, NMCs and OSSs, and a lack of raw network data.
  • Missing data — filtered extracts with no correlation, roll-up or cross-reference.

How it works

Poller/ETL engines extract raw data from network NMSs and third-party sources via REST API, SOAP/XML, TL1, CORBA and SNMP. Data is loaded into a raw database, then groomed and correlated into a master data set held in a column-oriented store. The stitching engine works on two levels — physical (network element, card, port, link) and logical (switching, routing, muxing, VPN, pseudo-wire and service), and runs both vertically and horizontally, within the same domain and across domains. Platform building blocks include extract engines, translate-and-load engines, a delta data loader, an audit engine, a correlation layer and write-back engines, supported by a GIS module, report builder, process engine and SQL query builder.

Capabilities

CapabilityWhat it does
Bulk data loadDaily loads at billions-of-data-points scale, multi-domain, multi-vendor, multi-technology, multi-format
Third-party loadIngests from provisioning, assurance, ERP, CRM, change management, facility management, fault management and infrastructure management
Topological stitchingPhysical and logical, vertical and horizontal, within and across domains
Refined network viewAll configuration data in a single database regardless of domain, vendor or third-party source
AuditingCompares data across vendors, technologies, network and external sources
Detect missing dataIdentifies and reports missing and bad data to ensure completeness
ViewsTabular inventory/topology, graphical topology including a spider view, asset detail and GIS

What makes it different

  • No pre-defined data models required — data is structured and stitched after loading, so the tool adapts to whatever the network and third-party systems actually contain.
  • Analysis across the entire available data set rather than a sample.
  • Absorbs heterogeneous sources — SNMP NMS, LLDP, planning data and raw config, and reconciles them.
  • Policy enforcement through the Flo process engine, so data integrity and quality become inherent to processes rather than after-the-fact clean-ups.
  • Fills gaps before replacing tools — designed to sit alongside an existing OSS/BSS ecosystem rather than force a rip-and-replace.

Service models by technology

NetTopo expresses each network technology as a stitched service model, linking RAN, backhaul, core and IT layers.

  • Mobile — 5G (gNodeB / NRCell), 4G (eNodeB / eCell), 3G (NodeB / RNC), 2G (BTS / BSC) and VoLTE (IMS with I-CSCF, S-CSCF, P-CSCF and related functions).
  • Fixed — FTTH broadband (NAP / OLT / ONU / BNG / CGNAT) and xDSL (MSAN-based).
  • Enterprise — national data services with CPE-to-CPE circuit stitching and SDN.

Worked example: FTTH port pre-allocation

At one operator, the existing allocation approach risked double-allocating customers to network access points and reported a local shortage of ports. Loading all NAP and customer data into a single database — around 120,000 NAPs (1.4 million ports) and 730,000 wire subscribers — the tool evaluated the possible permutations (84 billion), limited them to line-of-sight within 500 metres (about 35 million combinations), and pre-allocated a unique NAP per customer by shortest street distance and port availability. The finding: most customers could be served with existing capacity, and double allocations were avoided. Results were surfaced on a GIS and street-view interface.

Architecture & deployment

A cloud-native architecture organised into Apps, Use Cases, Platform and Cloud layers, running on a big-data framework with container and cluster orchestration, CI/CD, authentication and databases. Data can be extracted from any source and written back to any destination via multiple API and database interfaces. Deployment can be phased — in one Tier 1 European operator engagement an initial phase delivered end-to-end topology views from extracted configuration parameters, with a later phase adding configuration planning with templates and script generation, plus inventory and site correlation enriched with GIS.

Proven in the field

  • NetTopo is deployed and taught as a live module inside an Asia-Pacific operator group, described in that operator's L1 support training as the module used to identify and stitch network elements into an accurate representation of the network topology, working alongside a cross-functional database, device reconciliation and passive-element reconciliation components.
  • Digitata Networks reports being named Partner of the Year 2022 (OSS Team) in connection with that deployment.

Customers anonymised by region and tier.

Solves

proven at

related

supports vendor