*Introduction of FlinQ (EN)

Owned by Tom Polman
Last updated: Sept 15, 2022
4 min read

Technical Manual | TM-20210107-LG-01

Security Management | FlinQ 3.X |

Introduction

This manual explains the relationship between the different parts of FlinQ. This manual is not a manual on how to configure or update FlinQ, but an explanation of what is available and what is possible.

FlinQ is security management software with which various (security) systems can be displayed and operated with a map of the location as a basis.

A good security management system can be fully set up according to the wishes and requirements of the end user, and so is FlinQ. FlinQ can be linked with various brands and systems including;

  • Camera observation systems

  • Access control systems

  • Burglar Alarm Systems

  • Fire alarm systems

  • Intercom installations

  • Parking management systems

  • Etc.

FlinQ is an open and flexible integration platform that is perfectly adjustable for both small and large activities. The software used by the end user is FrontEnd. The GUI is characterized by a simple operation which is intuitive to use. The open and accessible interface is unmatched in the industry.

The graphical user interface (GUI) combines insights from the gaming industry and touchscreen technologies, offering an innovative and intuitive approach to security management.

Users can manage their systems from anywhere. Due to its simplicity, FlinQ is very easy to learn. It improves the overall efficiency of the security system and helps lower operating costs.

The GUI is created in FlinQ Studio. This defines the conditions of the installation, the levels the user is in and the actions associated with them. For example, it is determined here that when an Intercom call is triggered, the cameras come into view and the end user is given the choice to open the door.

In order to properly monitor how the system behaves, there is another FlinQ server Status program. This software shows the connections between the server and the external installations. The messages are also displayed here for technical purposes. This runs in the background without the user noticing.

FlinQ uses Structured Query Language (SQL) to store all data, this data is stored locally securely and can therefore be fully set up in accordance with the GDPR legislation.

FrontEnd

As mentioned earlier, FlinQ consists of several parts. FrontEnd is the program used by the end user. The end user has an intuitively working map with icons with which it is possible to navigate, request the status of external components and even start an intercom conversation.

This Frontend software is completely unique for each project, security is always customized, because the risk in a building is also not standard.

It is even possible to adjust the layout per user. If a user has rights to other floor plans, he can see a different layout than his or her colleague.

FlinQ Studio

FlinQ Studio is needed to set up FrontEnd.

FlinQ Studio is a clear program with which the floor plans, icons and flow charts are created. To be able to work with this software there are 2 essential conditions;

  1. The Service FlinQ Server must be running.

  2. There must be a connection to the SQL database, where it must then be possible to log in.

In the window on the left are the “Maps”, these are the maps as the end user will see them. When working in the folder, the work can be saved by means of the disk at the top of the screen.

Under Maps are the Devices, with the left mouse button they can be moved to a folder, where the size can be adjusted. The Device can be adjusted with the right mouse button.

It is also possible to work via the Maintain button. Then icons can be placed by means of a CSV file.

You can create and load a backup in 2 ways. 1, in FlinQ studio by the CSV files with the data about Name, Position, format ect. store.

Or, you can backup the database in SQL software.

FlinQ Status

With the program FlinQ Status you can see the status of all connectors.

This tool is mainly used during the business. Here you can monitor whether the connected installations are communicating.

A “connector” can be disabled, enabled and reset here.

In this software it is also possible to simulate a message after logging in. With this, for example, a one-time set or reset pulse can be given if this command is lost in the data network.