New Release: More reporting features and improved transparency

In the first release of 2021, we have updated the RoamsysNext product suite with many powerful features that will make your life easier. It includes enhanced reporting options for network countries, more transparency for our data capturing service, and the long-awaited option to import data via Excel sheets.

We are mostly working from home these days, and we have been using our time well to improve our products with interesting and helpful features that some of you were looking forward to, especially when it comes to reporting functionalities and transparency within our services. So let’s have a look at the most important improvements. You can find a complete list in the Release Notes section of the Launchpad.

For all information related to the coverage of your services, the country information is of course extremely important. All MNOs have one organisation country that is not necessarily related to the network coverage. Also a TADIG code always has one country code included, which is not precise enough as well, because a TADIG code can be used for more than one country. Just imagine some small countries or a network of islands, where your own coverage can be different from area to area.

To solve this problem, we have introduced covered areas for a while, which allow you to add multiple covered areas to one organisation. But with network mergers and political changes being a reality, even this doesn’t cover all possible use cases. We have decided to include another layer of covered areas that can now be added to single TADIG codes, and that can be used for example for the powerful country coverage report in our Networks module. This may sound a bit abstract, so let’s take a look at a concrete example to clarify the different results of the now four options:

As you can see, all four usable options show different results. With the newly introduced option #4, you now have all the flexibility you need to get realistic coverage reports for all scenarios. In addition to the reports, the covered areas for TADIG codes can now also be displayed in a separate column in your connections overview and can be used for the “World Map” and “Country Coverage” Dashboard gadgets, too.

To set up the covered areas for organisations and TADIG Codes just get in contact with support@roamsys.com, and we will help you to find the perfect set-up.

The more documents are included in your account, the better the results, especially with regard to network configurations. More and more organisations are distributing their IR.21, IR.85, IOT and OpData documents in RAEX format, which is highly appreciated as our system is updated with new documents in real time. But still, there are many documents not delivered in RAEX format, and this is where our data capturing service comes in. It allows you to send us your non-RAEX IR.21 and IR.85 documents, and we will make them available in the system, soon.

Since we set the highest standards for data quality, we carefully review each submitted document and compare it with previous versions. In case of suspicious discrepancies, we contact the operator directly to ensure that no incorrect configurations enter the system caused by errors in your partner’s document itself.

To increase transparency regarding the status of your submitted document, we have now added two status fields within your Data Capturing Status overview section available in your Documents module. It contains the estimated time frame until the document will be loaded into your system. There is also a comment section where we can inform you about any delays or issues with the submitted document.

We know that there are MANY Excel spreadsheets in the industry. From the beginning, we have offered exports across the data in excel and csv format. But until now, only the csv format has been supported for the import of data. We are now on the way to change this and offer convenient Excel-imports as well. It is already available for the most used sections like the footprint import in the Networks module. It will be available very soon for all other imports, too.

Some smaller improvements have been added to the Network Configuration Optimizer. The vendor-specific configuration templates have been updated to support ISO-2 and ISO-3 country codes. For users of the API, custom fields can now be included in the 3rd party API responses for change extracts, current extracts and configurations.