Status and Monitoring
Monitoring of components in the network
NeuroomNet monitors all integrated components. The components are displayed in a clear, filterable list. In regular operation, you can see at a glance whether all components are switched on when they should be switched on or switched off when they should be switched off (see Scheduling). The components either log on to the system or are actively included.
Quick overview through precise status display
If a component does not meet its target status, a corresponding status is displayed. With individually adjustable warning levels, you can define how critical the status is classified. For example, the failure of a network switch will have a higher priority than the failure of a printer.
Map based search in the building
All groups of the installation can be located in an overview map. If you select a group, the map view switches to the corresponding floor and the position is highlighted. Of course the search also works the other way round. If you select a group on the map, the list scrolls immediately to the corresponding entry and provides further information and actions.
Automatic failure detection
If a component fails, this is indicated immediately. The server monitors the components in the background according to their protocol. As soon as the error is corrected, the status is updated again immediately. All errors are of course logged.
Grouping for effectiveness
Components can be grouped logically. For example, components can be grouped into work centers, stations, exhibits. The descriptions can be freely selected. Groups can then be further grouped in any nesting depth, for example to rooms, floors, halls. This not only serves the purpose of clarity but also simplifies many processes. "Switch off 333 components" becomes "Switch off hall".
Extensive recording of status changes - Logging
On the one hand, logging helps to identify a system behind system changes, e.g. a component fails at the same time every day or always after a certain number of operating hours. Furthermore, statistical statements about technical components can be made which may be of interest when purchasing a new system. Since logging data can quickly become extensive, numerous filter options are available for evaluation.
Individual user interfaces - Dasboard
Control everything with one button click or a separate button for everything. User interfaces can be arranged as desired. The controls (buttons, sliders, etc.) can be connected directly to the end device or component or serve as triggers for media control. Of course, the dashboard interfaces work on the desktop and mobile devices.
Switching on and off - time controlled or manual
All components and groups with corresponding protocol can be switched individually. That means manually, by the administrator via the web frontend or by anyone who has the right via a button in the dashboard. Of course, this can also be automated and all switching processes can be controlled via a scheduling.
Scheduling - periods of time can be set individually
The scheduling offers very extensive possibilities. First of all, standard times can be defined. All exceptions to this have higher priority. For example, you can define any period of time for seasonal events such as holidays or individual public holidays. With a few clicks, for example, you can create an event on every second Friday of the month at 5:30 PM, between February and September.
Switching sequences - switching on and off according to plan
If the conference room is no longer needed, it can be switched off. First, send the projector the command to turn off. It may need to cool down a bit. In the meantime, raise the screen and the blinds. Then switch off the computer and audio equipment. And when everything is off, turn off the power. The sequence and waiting times can be freely defined - and only have to be defined once - and then all conference rooms behave in the same way.
Media control - logic editor
Every building is different and every media technology is used individually. The NeuroomNet media control system offers all the possibilities to easily define processes (actions) that are to be executed in response to specific events. Events can be, for example, a time, pressing a button on the tablet or exceeding a threshold value. For example, it is very easy to start an announcement every day at a certain time of day, or to call up a lighting scene and/or switch media sources at the click of a button. This opens up countless possibilities without having to learn a programming language or become familiar with the protocols of the terminal devices.
Actions and events for components
Components can perform different actions depending on their type. For example, a projector component can switch the shutter or the video inputs of the projector or a KNX component can call up different light scenes. The actions can be performed in different ways. Through manual access at administrator level, through automations of schedulers or media control or through dashboard elements (buttons, sliders etc.) for users.
Wishing visitors, customers or employees a "good morning", pointing out that the shop is closed, or praising the cake buffet on Sundays at 15:00, these are tasks that can be fully automated via the system.
Of course, one cannot or does not want to continuously observe the surface and the status of the system. Therefore the system can send messages via email. It is possible to define which persons should be notified about which events. For example, the person in charge can be informed when the heat map reports that the threshold values have been exceeded, or technicians receive a message as soon as a certain device is no longer accessible in the network.
Individual access rights via rights management
In the very flexible rights management, any roles can be defined, which in turn can be assigned any rights. So you can freely decide which user groups there should be. Users can be assigned any number of roles. So you can quickly make one person an editor or administrator, but also create users who can only observe.
Remote Content Management (RCMS) - Distribute media 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 on them can use or display this content. For this task a comfortable user interface is available, which enables these workflows in cooperation with a client software (Windows, Mac, Linux)
Complete operation via the browser
In order to be able to access the system from any workstation without prior installation, the complete front end is implemented in HTML5. This means that it is not only available across platforms (PC, Mac, Linux) but also on tablets and mobile devices. In doing so, emphasis was placed on a uniform user interface and simple operation.
Operation via mobile devices
The user interface is designed to be "responsive", which means that the interface adapts to different resolutions and screen sizes. Various functions that cannot be operated sensibly on small mobile devices and are rarely needed in everyday life are automatically hidden, displayed in a reduced size or managed in separate menus.
Secure communication via HTTPS
Secure communication is indispensable in building management. NeuroomNet is consistently designed for encryption. The system can therefore be operated in a standard-compliant PKI infrastructure with certificates. In addition, the system can also be integrated into a domain via Active Directory so that all participants can log on to the system using their domain password. If rights and roles are used, personal data is often also transmitted and the DSGVO (en: GDPR, fr: RGPD) prescribes encrypted transmission.