Skip to content

TelecommunicationsBI, AI and ML for the business

Antenna retilt, before and after

Two drive-test campaigns on the same route, before and after the antennas were retilted. Muvia compares them lap by lap and stretch by stretch: SINR, received power and throughput tell you whether the work paid off, and on which stretches.

Illustrative scenario: it describes a typical case, not a customer project.

The antennas have been tilted. Did it help?

A retilt is decided on complaints and counters, carried out in one night and often judged on gut feeling. The drive-test measurements exist, but two campaigns two weeks apart end up in two files and two slide decks.

In Muvia the campaigns sit in the same source, and the comparison is made on the same stretches at the same hours. A distribution, the overlaid lap and a stretch-by-stretch table settle the question.

Who it's for
Radio optimisation engineers, drive-test teams, regional network managers and whoever signs off work on the antennas.
Diagram: the drive-test measurements arrive as CSV files, before and after the work; the cell and stretch inventory from an Excel file; cell counters from the network management system over SFTP. Muvia produces the comparison between campaigns, the same lap overlaid, the SINR distribution and a stretch-by-stretch notebook.

In Muvia, step by step

Real product screens, recorded on a project with sample data.

1 of 5

The video · Two drive-test campaigns on the same route, before and after the antennas were retilted. Muvia compares them lap by lap and stretch by stretch: SINR, received power and throughput tell you whether the work paid off, and on which stretches.

What you get

A verdict, not an impression
Distributions and a stretch-by-stretch table say whether the work improved the network, and where it did not.
Like-for-like comparisons
Same road, same hours: the differences come from the work, not from the route.
All campaigns in one place
Each new campaign joins the earlier ones and can be compared with all of them.
The next job starts here
The notebook stays in the project, with the figures and the decision taken.

For the technical team

How it is built in Muvia

  1. 1

    Load the campaigns

    The files of the two campaigns enter the same source, with a column that tells them apart. Each new campaign is appended to the earlier ones with the same columns.

  2. 2

    Compare the distributions

    In Analysis a condition separates campaign B from A: the SINR distribution, the day-by-day box plot and the XY view of RSRP against SINR show the shift.

  3. 3

    Overlay the same lap

    Comparing with an earlier period lays today's lap over the one 14 days before: same road, same hours.

  4. 4

    Settle it stretch by stretch

    A notebook tabulates the SINR and throughput gain on every stretch, with the conclusion, and prints to PDF for whoever approved the work.

The data it needs
  • The drive-test van's measurements, one sample every 5 seconds: stretch, serving cell, RSRP, SINR, throughput
  • The campaign before and the one after the work, on the same route
  • The cell and stretch inventory, from an Excel file
  • The date and time of the work, as an annotation
Parts of Muvia used

Bring us a question you can't answer today.

We start from a real question your business has and walk the path from source to dashboard with your systems, not a demo dataset.