Tyrecheck’s cloud-based data warehousing and reporting modernization

amount of independent DWHs

the average time needed to load data for one customer database.

Have you ever forgotten to change your winter tyres in the spring (or your summer tyres in winter)? Is it time to replace your tyres with new ones? Can you figure out the parameters of your tyres?

You don’t need to fall asleep at the wheel anymore as Tyrecheck has a solution for you. Just check a report or simple dashboard (both defined by Adastra) via your PC or mobile device.

The data are downloaded from a cloud-based data warehouse solution that Adastra helped Tyrecheck build.

The problem we had to face

Tyrecheck (known as Tirecheck in the USA) offers a complete professional tyre management system and can equip you with gauges capable of automatically reading and transferring your tyre data to the appropriate database: an ideal service for tyre producers and dealers, garages, or for managing a bus line, a trucking company, even your corporate car fleet.


Tyrecheck customers can be found all over the world and with every customer having its database in the cloud, some reports were overloading source databases and making it difficult to provide joint reporting. The company realized that a Data Warehouse (DWH) redesign was needed and after some preliminary work, Tyrecheck ran into many technical problems which were beyond their scope. At this point they called Adastra.

“Adastra cooperated with us in an exceptional way, we thank Adastra consultants for their professionalism, support and commitment while constructing this robust data warehouse system with us.”
Juan Pablo Onofre, IT Project Manager, Tyrecheck

Adastra was asked to help Tyrecheck with two areas in particular

  1. to find an appropriate reporting tool to cover all databases and to provide easier reporting and better dashboards.
  2. to redesign the existing DWH solution which consisted of several independent data warehouses (each representing a single Tyrecheck customer). Today there are 35 DWHs, a number that will grow in the future as the number of Tyrecheck’s cus­tomers increase.

Our suggested solution

Initially, we focused on designing a new DWH to fulfill present requirements and to consolidate all customers and their related data. We customized the DWH on an MS Azure platform for each Tyrecheck customer. MS Azure runs on Microsoft’s global datacenter network. The MS Azure cloud platform is geographically redundant and virtually ensures high data availability (SLA 99.9 %). Data are easily and quickly accessible and can be readily and transparently reported. This is a boon for Tyrecheck and its customers as they rely on data security and scalability: services can quickly scale up or down to match planned and unplanned demands.


All customers now have their own tailor-made dashboard to meet their needs and expectations as data are designed just for them. Tyrecheck chose DataZen as its reporting tool and Adastra’s con­sultants competently integrated it into a Tyrecheck web environment incl. single sign-on request.


Although separate databases are not huge (Adastra is capable of working with hundreds of millions, even billions of records and there are only millions of records), the multiple databases of Tyrecheck were located around the globe in different time zones. While servers physically placed in Europe communicate with each other quickly, connecting to a server physically placed in America or Asia takes slightly more time, but the lag is insignificant and fully satisfies Tyrecheck and its customers.

What was the outcome of the project

The project was successfully finished and passed on to our customer with the first dashboards designed for Tyrecheck’s largest customers. After presenting sample dashboards to its customers, Tyrecheck discussed specific forms of dashboards and designed simplifications to suit each customer better (the less data displayed, the more transparent the dashboard and the better the view in mobile applications). Data are loaded on a day-to-day basis.

Key project benefits are:

  • Loading procedures from Stage to DWH are managed by metadata and associated parameters (a generated procedure can do this for selected customers). Tyrecheck specializes in using several DWHs (35 today with more to come in the future). Using an Adastra engine to generate ETL procedures would result in an unnecessary conflation of metadata and generated procedures (35 times), so Adastra adapted the engine to do everything once and to manage procedures by parameters.
  • Average loading time for one customer database is 5 minutes.

Who participated in the project

Jiří Balcárek
Ředitel divize Telco & Retail

Get inspired on our blog

Observability platform vs. observability tools 

Complex information systems fail in unexpected ways. That’s why IT teams need both observability tools and an observability platform. To understand the distinction between...

Read more

The Inevitability of Cloud Adoption Means A Challenge for Business Infrastructure Maintenance

The existing on-site infrastructure is gradually turning into a relic of the past, akin to the once-ubiquitous floppy disk. David Kaláb from Adastra outlines...

Read more

Unraveling the Future: Top 8 Data Management Trends for 2024 and Beyond 

The digital landscape is evolving at an unprecedented pace, and with it comes a new set of challenges and opportunities for IT professionals, data...

Read more