In the client-server architecture, all components integrated into the network are permanently monitored. All components are displayed in a clear, filterable list. In regular operation, you can see at a glance whether all components are switched on, if they are to be switched on, or are switched off, if they are to be switched off (see Scheduling). The components either log on to the system (e.g. computer or RFID reader) or are actively integrated (e.g. projectors or printers).
If a component fails, this is indicated immediately and further steps are taken accordingly. The server monitors the components in the background according to their protocol. As soon as the error is removed, the status is immediately updated again. The failure is of course logged in a logging system. For more information, see „Logging“
If a component does not correspond to its connection status, a corresponding status icons is displayed. If, for example, a computer is ‚off‘ although it should be ‚on‘ according to the schedule, this is displayed differently from a manually deactivated computer (for example, if this computer is temporarily not to be switched on). This provides a quick overview at any time, even over a large number of components. Of course it is also possible to filter by all different status.
All components of the installation can be located in an overview map.
If you select a component or a group of components, the map view switches to the corresponding floor and highlights the position. Of course, the search also works the other way round. If you select a module on the map, the list scrolls immediately to the corresponding module and provides further information and actions.
Components can be logically grouped. For example, components can be grouped into workplaces, wards, exhibits, rooms, and so on. The types or names of the groups are freely selectable. Grouping does not only help with clearly arranged working but also simplifies the communication between the components. Means to lead information from one component to another.
the one hand, logging helps to identify a systematic behind a process, e.g. a
component fails every day at the same time or always after a certain number of
operating hours. Furthermore, statistical statements can be made for components
that can be important for a new purchase.
Since logging data quickly becomes confusing, numerous filter options are available for evaluation.
All components (or component groups) with corresponding protocol can be switched individually. This means manually, directly via the action of the component or group or manually by creating a button that switches all or a group of components. This can of course also be automated and all switching operations can be controlled by a scheduling (see Scheduling).
The Scheduling offers very extensive setting options. First of all, standard times can be defined. All exceptions have higher priority. For example, you can define any periods for school holidays or individual public holidays. The actual switching times are displayed for each day in order to keep track of the situation at all times.
If you want to switch a group of components on or off, you don’t necessarily want to switch them all at the same time. Actions like switching off the computer, switching off the projector, waiting a while until both are shut down and then switching off the corresponding power socket, can be set individually for all component groups in the Booting-Order dialog.
Components can perform different actions depending on the type. For example, a projector component can switch the projector’s shutter or video inputs, or a KNX component can call different light scenes. The actions can be performed in different ways. Through manual access to components or group level or through events in the logic editor.
Events can trigger actions. Events can be, for example, a time, pressing a button or exceeding a threshold value. For example, it is very easy to start an announcement every day at a certain time or to call up a lighting scene and/or switch media sources with a click of a button. This possibilities are endless.
One button click for everything or a button of your own for everything. In a separate editor, buttons for triggering logic sequences can be put together as desired. Buttons can be colored or grouped. Of course it is also possible to determine for each button which user rights you have to have in order to activate it. The buttons can also be used to quickly perform actions on a mobile device.
Wishing visitors a „good morning“, pointing out the closure, or advertising the cake buffet on Sundays at 3 p.m.: these are tasks that can be fully automated via the system.
Of course one cannot or does not want to observe the surface and the status of the system continuously. Therefore, the system can send push messages via email. It is possible to specify which persons should be notified of which events. For example, the person responsible can be informed if the heatmap reports that the threshold values have been exceeded, or technicians can receive a message as soon as a particular device is no longer accessible in the network.
In the very flexible rights management, any roles can be defined. To any role any right can be assigned. For example, you can define that a user with the role „Admin“ is allowed to create buttons, a user with the role „Supervisor“ is allowed to use the button and a user with the role „Editor“ doesn’t see the button because he is only allowed to access CMS content.
It does not belong to a classic CMS, but is often meant by it. You want to distribute media (images, videos, etc.) from a central location to different client computers so that the applications running there can use or display this content. For this task a comfortable interface is available, which enables these workflows in cooperation with a client software (Windows, Mac, Linux).
Template-based content in HTML format can be compiled directly in the system. A preview function allows a comfortable working method. Since templates of course do not always fulfill all design ideas it is optionally possible to extend the system by individual templates.
The system can not only control digital components (computers, projectors, etc.) via their protocols, but also the corresponding sockets. By grouping components, the system automatically knows which component belongs to which power source. An integrated KNX server communicates with any number of bus couplers.
Ideally suited for accessing the system from any workstation, the complete frontend is implemented in HTML5. This means that it is not only available across platforms (PC, Mac, Linux) but can also be used on tablets and mobile devices without installation.
The user interface is responsive, which means that the interface adapts to different resolutions and screen sizes. Various functions that cannot be used sensibly on small mobile devices and are rarely needed in everyday life are automatically hidden, reduced in size or managed in separate menus.
If several people work on one system at the same time, overlaps can occur if, for example, two people want to edit a text in the CMS at the same time. Therefore, the system blocks the article from being edited by other users. In addition, the user is displayed who has just opened the corresponding article for editing. The same applies to many internal administration tasks such as component management.
In order to manage the computer systems in the network or to execute actions on the computers, a client application must be installed on each computer. A platform-independent application is available for this purpose. Windows, Mac and Linux systems are supported. Among other things, the computer can be shut down via the application, a maintenance screen can be displayed (Windows) and also the file storage (RCMS file copy) functions are managed via this. There is also a server available to automatically distribute updates of this application.
The system provides an API (Application Programming Interface) for ‚third party‘ applications, which can be used to perform numerous functions. This enables manufacturers of individual software to make database queries for visitors or media content. The system can also take over the file handling for the applications via the API if, for example, users create content for the applications that are to be managed centrally. The API also determines the status of the applications to visualize it accordingly.
order to securely log on different users with different rights, it is highly
recommended to encrypt this communication. The system can therefore be operated
in a standard-compliant PKI infrastructure with a standard-compliant OAuth
Optionally, the system can also be integrated into a domain via Active Directory access, so that all participants can be logged on to the system via their domain password.
If rights and roles are used, often also personal data are transmitted and the GDPR (de: DSGVO, fr: RGPD) prescribes an encrypted transmission.
The system has a built-in documentation. In each dialog, the ‚Help‘ function provides access to extensive documentation corresponding to the dialog currently displayed. A ‚Search‘ function makes the documentation even more convenient.
Data exchange with ERP systems (ticket prices, events, etc.)
RFID systems connection (e.g. access control or visitor identification)
counting with threshold value functions
Third party media devices connection such as projectors, cameras, etc.
Authentication via standard OAuth server
Cloud synchronization of media content
Authentication via standard OAuth server
Client API for software integration from third-party manufacturers, e.g. games
The system cannot mow lawn at present