Closing the Loop Between Network Inventory & Field Operations

Network inventory systems precisely record network infrastructure data—provided that the information is kept up to date. In practice, however, the alignment between the system’s view of the network and its actual state in the field can gradually erode.

The pattern is simple and recurring. A technician arrives at a network node equipped with data from the inventory system. Upon arrival, they discover that a previous crew changed the configuration, but there’s no trace of that visit or the modifications in the system. The technician wastes time assessing the situation and calling the coordinator. Their own visit report is then logged into the inventory with a delay of several hours. The next crew arrives facing similar blind spots.

The network inventory gradually loses its operational value, not due to the system’s limitations, but because of a lack of a mechanism to close the loop between network data and day-to-day field operations. The larger the scale of operations, the higher the cost of this gap, resulting in prolonged fault resolution times, unsuccessful field visits, and the declining credibility of the PNI (Physical Network Inventory) as a reliable source of network data.

Key areas where discrepancies between the system and field reality emerge

The gap between what an inventory system (such as Smallworld PNI) records and the actual state of the network grows fastest in three main areas:

1. Handling emergency tickets during a scheduled workday

Every field service organization operates in two modes simultaneously: executing scheduled work orders and responding to emergencies. An emergency ticket popping up in the middle of a planned workday requires an immediate decision on which technician has the right skills, availability, and necessary equipment to fix the issue.

Without a system that integrates PNI data with technician availability and qualifications, making this decision consumes valuable time and increases the Mean Time to Repair (MTTR), directly translating to a risk of SLA breaches. As the outage awaits resolution, schedules are disrupted. Furthermore, changes made during such emergency interventions often don’t make it back into the inventory, because completing the task takes precedence over updating system information.

2.Reporting without cellular coverage (offline work)

Many maintenance tasks take place in areas with zero connectivity—inside telecommunication ducts, enclosed nodes, or building basements. Tools that require a continuous internet connection fail to meet the demands of working in such conditions. Consequently, visit data either remains completely outside the system or enters the PNI with a significant delay, widening the gap between the network records and reality.

3. Subcontractor work outside the inventory system’s control

Large telecom operators rarely maintain their networks using only in-house resources. Technical partners (subcontractors) carrying out fieldwork often report task completion using their own proprietary workflows. Without a centralized work order management system, dispatchers lack real-time visibility into task progress, and network modifications made by external crews might reach the PNI with massive delays—or sometimes not at all.

Where multiple partners operate without proper data access separation, an additional problem arises: specific network modifications cannot be attributed to a particular crew or work order. The network inventory becomes a shared resource with no clear owner, which directly compromises its reliability.

Smallworld PNI and GeoTask integration: closing the operational loop

The integration of GeoTask with Smallworld Physical Network Inventory addresses each of the aforementioned areas, successfully closing the information flow loop between the network inventory and field operations.

GeoTask is also compliant with TM Forum standards, ensuring streamlined integration with the existing IT environments of operators adhering to these standards, eliminating the need to adapt interfaces or build intermediary data layers.

Automated dispatching with skills and equipment verification

Tasks created in Smallworld flow directly into GeoTask and are assigned to a technician who simultaneously meets four criteria: they possess the required skills, carry the necessary equipment, are available within the specified time window, and are optimally located.

An emergency ticket injected into a planned schedule triggers automated route recalculation and notifies technicians of the changes, without requiring the dispatcher to manually intervene in every single case. Along with the assigned work order, the technician receives all location details within their mobile app, including the history of previous visits and infrastructure data pulled straight from Smallworld PNI.

If a technician requires broader network context while on the job, a single click transitions them from GeoTask to the Smallworld web viewer. The viewer opens precisely at the task’s location, displaying a full, up-to-date view of the network state in that area.

Offline synchronization: zero-delay field data

The mobile app is fully functional in offline mode. Data, photos, and status updates are saved locally on the device. Once connectivity is restored, automatic synchronization occurs, preserving the actual, real-time timestamps. Modifications recorded by the technician flow directly into Smallworld PNI, eliminating manual data entry and delays caused by poor signal coverage.

Subcontractor management with segmented data access

GeoTask supports a multi-subcontractor collaboration model. Different organizations, operational regions, and collaboration setups with dispatchers and technicians can all be managed within a single system. The operator retains comprehensive visibility over all field operations, while each subcontractor only accesses the work orders and data explicitly assigned to them. Every network modification is linked to a specific crew and work order, virtually eliminating the issue of untraceable PNI updates.

Integrating Smallworld PNI with GeoTask: a Polish telecom operator case study

One of Poland’s leading telecommunications operators, Play, serving over 2 million subscribers, successfully implemented GeoTask integrated with Smallworld PNI.

Here are some of the key outcomes of this implementation at Play:

Time from ticket creation to technician dispatch reduced to just a few minutes.
A significant reduction in Mean Time to Repair (MTTR) for HFC and xPON network outages.
Complete visibility into nationwide field operations, regardless of which subcontractor executes the order.
Simplified and automated financial settlements with external technical partners.

UPC Poland (Play) – More efficient network management and streamlined field fault resolution

Read our case study

GeoTask and Smallworld integration: see it work on your custom scenarios

Every Smallworld PNI implementation is unique, varying in system versions, integrations, and operational models. If you’d like to see how GeoTask fits your specific use case, we can show you during a tailored demo based on your own scenarios: your network type, subcontractor collaboration model, and outage handling workflows.