BLOGINTEGRATIONMENDIX
Sven Spierings & Teun Salters

Meet TIM: the Step Towards Streamlined Monitoring

Enabling seamless communication between two systems is the key to success in the increasingly connected business world. But what happens when managing multiple CPI environments becomes a challenging and time-consuming task? Meet TIM—the groundbreaking solution that forever changes integration monitoring. This innovative application is powered by a Mendix front-end and an AWS back-end, and is designed to effortlessly collect and display crucial CPI data on one intuitive dashboard. In this blog, we explain TIM's capabilities in detail.

A brief introduction to AWS back-end

Let's start with a brief explanation of the back- and front-ends on which TIM runs. The back-end is AWS. AWS, or Amazon Web Services, is a collection of web functionalities used to build applications. It offers a wide range of capabilities, from storing data in a datalake to creating an API.

A brief introduction to Mendix front-end

Mendix is a handy platform that allows you to quickly build your own business app. It is a low-code platform, which means you don't need programming knowledge. Using visual and intuitive tools, you can build apps without too much coding. A big advantage of Mendix is that it can easily collaborate with various SAP systems and cloud services (such as AWS). This means you can exchange information between Mendix and other systems easily, so that everything can communicate well with each other. Another advantage is that Mendix is modular and fast! Finally, Mendix has its own cloud environment. This means you can host and manage your apps in the cloud, making them always accessible to you and your users.

What does the Mendix dashboard look like?

The dashboard is one of the most important features of the Mendix app. The dashboard provides a good overview of the most important information. But also where possible problems can be found in the system. An integration specialist can see here well which messages and flows are not running smoothly, but also which tickets belong to them. The users, tenants and AWS Endpoints, are managed in the app by the McCoy functional admins. They determine which user has access to which environment and whether that user is allowed to perform a certain task.

Some benefits of a TIM implementation

Working with TIM has several advantages. First, we can improve our service, but we also learn from improvements we have made before. This means we can spot errors faster and work towards a solution in the future. Below are some benefits of TIM:

  • TIM retrieves data from CPI environments and stores it in a datalake. A datalake is a large, minimally structured database where raw data is stored.

  • Data in the datalake is reduced and indexed to reduce storage and enable faster access to information.

  • The data is kept for various reasons, including improving the service, predicting errors, and enabling recalculation.

  • The datalake receives data, filters what is needed for specific datasets, and stores this filtered data. The filtered data is processed and analyzed to identify errors, detect changes in processes, and perform other functionalities.

  • A REST API ensures that the Mendix dashboard can display the analyses.

  • The API provides CRUD functionalities and webhooks.

  • The Mendix dashboard mainly uses the statistics that TIM has calculated, such as showing successful and error processes, graphs, and specific interface errors.

Better customer service

TIM provides a significant improvement in customer service. It automatically creates incidents for every error in the CPI environment and ensures that these incidents quickly reach the customers. This is done through the connection to external ticket systems such as Jira and Topdesk.Once an incident is created, the integration specialists receive an immediate notification. With one click of the button, the incident is converted into a ticket in the customer system. From that moment on, the two systems remain synchronized: every change in one system is automatically updated in the other.

This ensures that both the integration specialists and the customers can work in their own systems, but can also actively communicate. With TIM, communication between customer service and customers becomes more efficient and transparent, resulting in an improved customer experience and faster problem resolution.