Briefly about Tretus

17 December

What is Tretus? How can it help me to have facility management firmly in hands? What do I need for its operation?

Briefly about Tretus

Let’s start with why was the Tretus system created. Tretus was originally developed for checking the guards. It checked the guards if they do patrols. The benefit of Tretus for its users was an overview of the performed patrols and attendance. The guards forgot less to go on patrol. In case they did not start the patrol, were not on time at the shift or finished the patrol incomplete, the user was immediately notified.

With the gradual development Tretus got additional features which enabled to use it in other segments. Today, Tretus is a tool that helps our clients to have a better overview about projects, it saves time to managers in checking and reporting work, it makes the communication between the supplier and customer easier and, last but not least, it increases the efficiency of the work of the entire team.

Tretus system works on the SaaS model (Software as a Service). This model offers effective implementation of SW, because it minimizes cost of its acquisition and operation. Because of Tretus, you do not have to buy servers, deal with their maintenance and security, we will take care of it. You do not even have to install it to a computer. All you need for its operation are 3 inseparable parts and internet connection. These parts are web application, terminal and NFC tags.

 

Web Application

The web application is used for managing Tretus. You can launch it using your web browser. It is used for setting the entire system and to read data collected by terminals and that are saved on the server. What does it mean for the user? Each user, who logs into the Tretus using their details, will see what is happening on his projects and what events they should deal with. In the web application of Tretus the users will find reports about patrols done by guards, reports about cleaning, reports about defects for individual projects, etc. At the same time, here they can change the settings of the rules which should be monitored by Tretus, add user or delete finished project.

We can easily adapt the entire system thanks to setting roles of the users and responsibilities of your company according to your request. It means that the users of (not only) web application will not see what they do not need and they will use only the features that they are supposed to use.

 

Terminal

This part of the system will be used mostly by your field workers. This is a mobile phone with Tretus SW. We supply the terminal to our customers with installed SW, then it only has to be connected to the project. Terminal functions: it reads chips, it notifies the employee of upcoming activities, it allows you to take photos, make phone calls, send SMS.

For better idea an example from experience:

Upon arrival at work, the guards reads their personal chip. Tretus (and you) knows that they are at work. It tells them when to start the patrol and it tells them what points to check. During the patrol the terminal can acquire set types of reports (e.g. defect). The guards take a photo to add to the report, sign it and send it. Tretus will automatically send the report to specified people. The terminal also allows the guard to call or send SMS, but only to authorized contacts. You do not have to worry that the terminal would be used for browsing the internet or other activities. We have that under control.

Using the terminal, it is possible to assign NFC tags to employees and checkpoints. This is done only by the users who are authorized to do so.

 

NFC tags

The smallest but equally important part are the NFC tags. These are chips that, thanks to radio technology, you read at a short distance. They do not need any power supply and they do not emit any signal by themselves. These chips are then used by your employees to log in to the terminal, or you can use them to mark the checkpoints that the employee is to visit. Reading the chips is simple, it is enough for the worker to attach the terminal to the chip. The terminal then recognizes whether it is a chip of a checkpoint or an employee and according to this, for example, registers the employee for a shift or starts a patrol.