Access audit next month and permissions still in a spreadsheet?→ sara.next
braf.tech

Case study · Custom software

Planning and delivering the construction of high-voltage lines

A web platform with map, configuration and statistics modules brought order to investments previously run on paper and in spreadsheets.

The EnsysTM platform on a laptop and phone
Key result
50%shorter route planning time
Project
EnsysTM
Industry
Energy
Solution
Mobile and web application
Delivery time
2 months

Challenge

Starting point

Planning, preparation and delivery of investments were run on paper and in spreadsheets. The result was delays in communication between design offices and field teams, errors in routing and calculations, and no single repository of project knowledge.

Projects often exceeded budgets and schedules, and scattered data made quality control, auditing and change tracking difficult.

Solution

What we built

We built a flexible platform made of three modules. We added full event logging, permission control and change auditing, so the system meets security requirements and industry standards.

01

Map module

An interactive map integrated with OSM for plotting spatial data and planning the line route.

02

Configuration module

Dictionaries of parameters, such as pole types and soil classification, adapted to each project.

03

Statistics module

Dashboards and reports analysing work progress, costs and resource use.

Benefits for the client

What each team gained

The same change looks different to someone in the field, to management and to the audit. That is why we describe it three times.

Design offices

A route planned on one map

Spatial data, pole types and soil classification are in one place. The designer does not assemble them from several spreadsheets.

Field teams

The same data as in the office

The platform replaced the flow of paper and spreadsheets between office and site, so both sides work on the current version of the project.

Investment control

Progress, costs and change history

The statistics module shows work progress and resource use, and full event logging makes it possible to trace who changed the project and when.

Results

What changed after rollout

  • Route planning time reduced by 50%
  • Configuration errors reduced by 40%
  • A central repository with full change history
  • Compliance with the audit and documentation requirements of the energy operator
  • Scalability and the option to integrate further modules

A practitioner’s view

Why a single repository shortens planning

In linear infrastructure projects an error rarely comes from a lack of knowledge. More often it comes from two people working on different versions of the same data. A spreadsheet sent by email can be out of date the moment it is sent.

A central repository with parameter dictionaries removes that cause: a pole type or soil class is picked from a list rather than typed in. That is where both shorter route planning and fewer configuration errors come from. Change history is a consequence of a well-designed data model and, at the same time, what the audit asks about.

How to tell it is working

  • The project has one current version, available to office and site
  • Parameters come from dictionaries, not manual entries
  • Every change can be attributed to a person and a date

The application in action

See what EnsysTM looks like

  • Project view: statistics, map and work progress

    Project view: statistics, map and work progress

  • Map preview with the line route

    Map preview with the line route

  • Project statistics

    Project statistics

  • A dialog in the project view

    A dialog in the project view

Facing a similar challenge?

Tell us about the process you want to put in order. We will show you where it is worth starting.