Utility network GIS and field crew management system

The brigade receives the location, scheme and task of the network object. The work done and the changes noticed are passed to the professionals who maintain the network data.

The strip, the device and its real position are differently recognized in the map, maintenance and work records. The brigade or analyst is based on an outdated object and its unreliable technical history.

How the solution works

  1. The unit of property is linked to technical history and the applicable maintenance basis.
  2. The need for work is prepared according to a real scheme, materials, competence and a permitted window.
  3. An authorized employee of the operator certifies that the necessary conditions have been created for the work.
  4. The brigade provides performance, real replacement, test and remaining limitation.
  5. The controller accepts the change of property, and the course of the incident or maintenance receives a verified result.

Key challenges

  • The network register does not reflect completed changes
  • Maintenance of networks and facilities is often only started when a fault occurs
  • Field work, network closures and materials coordinated separately

Solution capabilities

Device code, location and data

The section of the network indicates the location of the equipment, the installation and the history of its changes and repairs.

Need for care

The technical basis applied and the necessary terms are combined with actual use and condition.

Work Package Prepared

The scheme, part reservation, competence and dependent operations are checked for the selected scope.

Valid information in the field

A version of the copy used and timing are visible; a reliable message action is provided for critical change.

Actual replacement

The brigade provides a true change in installation or geometry and proof of it for viewing network data.

Technical Completion

The result of the verification and the remaining work is separated from the final GIS acceptance and restoration of the customer service.

Business context

The network register does not reflect completed changes
The strip, the device and its real position are differently recognized in the map, maintenance and work records. The brigade or analyst is based on an outdated object and its unreliable technical history.
Maintenance of networks and facilities is often only started when a fault occurs
The maintenance plan does not link the technical basis of a specific asset, the necessary terms and real working conditions. The required verification is omitted or carried out without proper parts and a permitted work window.
Field work, network closures and materials coordinated separately
The brigade task does not receive a reliable scheme, real network status, materials and authorized work readiness. The work has to be stopped or repeated departure due to a gap to be known in advance.
Brigade work helps prepare for next service
An updated network schema and a record of the repairs carried out are needed not only for the current task. Next time, a team working in the same location can prepare faster and more accurately inform affected users. The customer gets a clearer history of infrastructure and a basis for planning future work.

Core features

  • Device code, location and data
  • Need for care
  • Work Package Prepared
  • Valid information in the field
  • Actual replacement
  • Technical Completion

Key integrations

GIS and Technical Register
Network schema, object codes and approved changes.
The course of network operations
Work window, permitted condition and work-related incident.
Warehouse and Resource Plan
A real critical part reservation and the right team.
Mobile Performance
Actual action, proof, test and proposed change of property.

Potential impact (%)

The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.

Avoiding repeated departures

12–42%Decreasing

This illustrative scenario assumes that 30-60% of errors can be addressed through the data and rule checks described. That share is assumed to fall by 40-70%. Company data is needed to verify both the addressable share and the resulting change.

Counting returns due to a fixed readiness gap, separating the planned technical phase.

Delays in the acceptance of a change of assets

6–25%Decreasing

This illustrative scenario assumes that 20-50% of waiting caused by missing information or unclear responsibility can be addressed. That share is assumed to fall by 30-50%. Company data is needed to verify both the addressable share and the resulting change.

The time between the duly submitted amendment and its adoption in the master register is measured.

Conditional calculation scenarios. The assumptions have not been validated against client measurements.

When this solution is relevant

  • Network changes made by crews do not occur in time on the map used by the dispatcher.
  • The work is appointed before checking that the required parts have already been delivered and reserved.

Implementation requirements

For the connection between GIS and field works, a structure of property is prepared, relevant schemes and procedures for updating the repairs performed. Data used by crews, work without connection and critical changes messages are combined with operator readiness and safety procedures.

Further development options

  • Mobile submission of performance and changes for additional types of work
  • Adjustment of care needs according to verified history of recurrent defects

Frequently asked questions

Adapting the solution to your business