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 integrated.
Quick overview due to accurate status display
If a component does not correspond to its target state, an appropriate status is displayed. With individually adjustable warning levels, you can determine how critical the condition is to be classified. For example, a network switch failure will have a higher priority than a printer failure.
Search via building plans
All groups of the installation can be located on an overview map. If you select a group, the map view changes to the corresponding floor and the position is highlighted. Of course, the search also works the other way around. If you select a group on the map, the list immediately scrolls to the corresponding entry and provides further information and actions.
Automatic failure detection
Should a component fail, this is indicated immediately. The server monitors the components in the background according to their protocol. As soon as the error is eliminated, the status is immediately updated again. The failure is of course logged.
Grouping for effectiveness
Components can be grouped logically. For example, components can be grouped into workplaces, stations, exhibits. The designations are freely selectable. Groups can then be further grouped to any level of nesting, for example to rooms, floors, halls. This is not only for clarity but also simplifies many processes. “333 Turn off components” becomes “Turn off hall”
Extensive recording of status changes
On the one hand, logging helps to identify a systematic behind system changes, e.g. B. if a component fails at the same time every day or always after a certain number of operating hours. Furthermore, statistical statements can be made about technical components that can be of interest when purchasing a new one. Since logging data can quickly become extensive, numerous filter options are available for evaluation.
Control everything with a button click or a separate button for everything. User interfaces can be put together as you wish. The controls (buttons, sliders, etc.) can be connected directly to the end device or component or serve as a trigger for media control. Of course, the dashboard interfaces work on desktop and mobile devices.
Switching on and off – time-controlled or manual
All components and groups with the corresponding protocol can be switched individually. With manual switching, the administrator acts via the web front end or authorized persons can trigger a button in the dashboard. The circuit can of course also be automated, so that all switching operations are controlled by scheduling.
Scheduling – time periods individually adjustable
Scheduling offers a wide range of options. First of all, standard times can be set. All exceptions to this have higher priority. For example, you can distinguish between any time periods for seasonal ones, e.g. B. Define holidays or individual public holidays. For example, with a few clicks you can create an event every second Friday of the month at 5:30 p.m. between February and September.
switching sequences –
Switch on and off according to plan
If the conference room is no longer needed, it can be switched off. First send the command to turn off the projector. It might need to cool down a bit. In the meantime raise the screen and the blinds. Then switch off the computer and audio technology. And when it’s all off, turn off the power. The order and the waiting times can be freely defined – and only have to be defined once – and then all conference rooms behave the same way.
Media control – logic editor
Every building is different and every media technology is used individually. For this purpose, the NeuroomNet media control offers all possibilities to define processes (actions) that are to be carried out on certain events in a very simple way. Events can e.g. B. a time, pressing a button on the tablet or exceeding a threshold. An announcement can be started very easily every day at a certain time, or a lighting scene can be called up with the click of a button and/or media sources can be switched. This results in countless possibilities without having to learn a programming language or familiarize yourself with the protocols of the end 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 carried out in different ways. Through manual access at administrator level, via automation of schedulers or media control or via dashboard elements (buttons, sliders, etc.) for users.
Wish visitors, customers or employees a “good morning”, point out the closure, or advertise the cake buffet on Sundays at 3:00 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 messages via email. You can specify which people should be notified of which events. For example, the person responsible can be informed if the heat map reports that the threshold values have been exceeded, or technicians receive a message as soon as a specific device can no longer be reached in the network.