How Pretius modernized a nationwide fiber-network monitoring system

The client is a national telecommunications operator in Central Europe that runs a nationwide fiber-optic network. Its platform is a network-monitoring system used both by the operator's own operational staff and by its business customers, who rely on it to keep visibility over the services that run across that infrastructure.

Network monitoring is an unforgiving domain. The people using the tool are often watching for the early signs of a fault, tracking whether services are meeting their SLAs, and deciding how urgently to respond. Everything about the interface either helps them do that quickly or gets in their way. When the same action is performed differently in different parts of the system, or when a topology view slows to a crawl because there are too many devices on screen, the cost is not just irritation. It is slower detection and slower reaction on infrastructure that carries real traffic for real customers. That is the context in which the existing system had begun to show its age, and it is why modernizing it was an operational priority rather than a nice-to-have.

Pretius began with a comprehensive technical and functional audit of the existing system, and that audit became the foundation of the new design. The solution rebuilt the front-end layer on Angular 11 and optimized the Java 11 back end, concentrating engineering effort on the areas the audit identified as holding the system back.

Three elements defined the build. An extended network-topology management model gave operators richer ways to manage and visualize the network's structure. An integration with Grafana, embedded through iframes with dedicated navigation into the statistics, brought monitoring metrics into the operator's flow. And a systematic unification of the interface established shared patterns for adding objects, displaying details, and filtering, so that the system finally behaved consistently from module to module.

The engagement ran as a fixed-price project using Agile methods, and its defining organizational feature was a co-development model. Pretius owned the front end while the operator's own architects and back-end developers owned the back end. This arrangement solved a real problem, namely the client's gap in front-end capacity, by pairing Pretius's front-end expertise with the operator's deep knowledge of its own back-end systems. It was not the path of least resistance. Co-development only works with tight synchronization and clearly defined API contracts between the two sides, and getting that coordination right was itself a significant part of the work.

The project was structured across distinct stages, with analysis, UX/UI, and development running in the first stage from September to December 2022, and a second stage covering topology and data-synchronization optimization running from November 2022 to February 2023. An optional third stage extended the work toward dashboards and deeper Grafana integration in early 2023.

Like any tightly scheduled modernization, this project carried real risks, and the team went in having named them in advance. Most of what could go wrong was anticipated and planned for, which is why the stages delivered on schedule.

The operator did not need its network-monitoring platform torn down and rebuilt from nothing. It needed the parts that were hurting daily operations fixed, namely a fragmented interface, performance that buckled at scale, and missing topology capability, while the proven integration layer underneath stayed exactly where it was. By starting with a thorough technical and functional audit, rebuilding the Angular front end, optimizing the Java back end where it counted, and running the whole thing as a tightly synchronized co-development effort, Pretius delivered a modernized platform that visualizes the network at full scale, unifies the operator experience, and comes with the documentation and backlog to keep evolving.

The clearest verdict on the work is the client's own response to it: a smooth delivery that turned into an extended partnership and further development. For any organization weighing a rewrite against a targeted modernization, this project is a reminder that the most valuable engineering decision is often knowing what not to rebuild.