Everything is component
Components are the molecules of the NeuroomNet system.
NeuroomNet has numerous interfaces. If “something” is connected via one of these interfaces, be it dedicated hardware, software or another endpoint, then we call it a “component”. There is probably no really universal name that sums everything up, so we decided to use the term “component”.
Why is this important or why do I need to know this as the installer of a system?
Components are the basis of our billing system. If you don’t have many components, you only need a few licenses. We offer licenses in packages. So you don’t need to know the exact number of your components up front, but a rough idea will help you decide which package you need. Of course, the packages can be expanded at any time.
Here are some examples to clarify:
A video projector is a component.
A projector that is connected to the system via a network is a component from the system’s point of view.
It doesn’t matter which protocol is used for the communication, be it a “universal” protocol like PJLink or a proprietary protocol.
A socket can be a component.
It depends on whether you want to address this socket separately. If we assume KNX as the interface, then the electrician should have assigned an address to each socket. However, if there is only one KNX address to switch all sockets (of a room, a floor) together, then all of these sockets are only one component in NeuroomNet.
A PC is a component.
The NeuroomNet PC client (software tool) is installed on the PC.
From then on, the PC is a component. The system can then turn off the PC, turn it on, reboot, or just detect if the PC is running. Incidentally, the NeuroomNet PC client is independent of the operating system and can integrate Windows, Linux and Apple PC systems.
A piece of software on the PC is a component.
A POI software, a digital signage software or a game is a component. For this, the software only has to use the API, which informs the system whether the software is running. Various other functions, such as a CMS connection, can also be made available via the API.
The smallest unit in NeuroomNet is always a component.
The type of component is determined by the interface protocol, e.g. KNX, TCP/IP, PJLink, DMX, SNMP etc.
In addition, a component can also have a component type in order to better specify the component. Let’s take the example from above again, the KNX component. Basically, NeuroomNet only knows the interface (KNX) and the address. But now, as an administrator, I can still assign the component type, either the socket in question, or light, or a heating actuator, or, or.
The same goes for most component species. An SNMP component can be of type printer, network switch etc. and a DMX component can be of type moving head spotlight or smoke machine etc.
You don’t have to assign a component type, but it gives you the option of switching lights and sockets separately, for example.
have components Features :
They all have the properties name and type in common. The name can be freely assigned and the type results from the protocol. In the case of the socket would be the type z. E.g. KNX. A type can optionally be assigned. Components may also have other properties that depend on the component type, e.g. IP address, bit width, etc.
have components Actions :
Depending on the component, different actions are available. In the case of the socket, these are usually only switching on and off. In the case of the video projector, these are a few more such as switching on, switching off, shutter-on, shutter-off, input HDMI1 etc.
Groups of components
Complex multimedia installations are more than a random collection of devices and software. These are usually grouped in some way during the planning stage: be it by room or individual stations such as exhibits or workplaces. This makes it clearer which devices are responsible for what and how they work together.
However, this grouping can be subdivided and named differently depending on the project. That’s why you can flexibly build and name a tree structure in neuroomNet.
Let’s take a museum as an example:
A digital exhibit as the smallest unit could consist of a computer, two projectors and an RFID reader. So we need a group type “Exhibit”. But there are also other stations that cannot be directly designated as exhibits. So we also need the group types “Digital Signage” for information displays and “Workplace” for the employees. These three types of groups are all on the same level, which we call “Station” in this example.
Let’s imagine a small digital signage station in the foyer that welcomes visitors with various images and videos or even interactive content. This station consists of a computer, software that plays the content, a beamer to project the output onto the wall and the whole thing should be disconnected from the power supply after it has been switched off.
For this we simply group our components.
Now all components of the group can be addressed together. Turning off the group will automatically cause every component in that station to turn off.
A switching sequence is used to determine in advance that the socket outlet is the last to be switched off after time X or that various devices are switched on first and then wait before the other devices are switched on.
Groups can also be switched on or off automatically via a circuit diagram.
If you group components, only the group appears in the building plan.
For the status of a group, the highest warning level of its child components or child groups is always passed up.
Nest groups further
In order to be able to work with the system as comfortably as possible, it can make sense to nest groups in further groups. At the lowest level, components are grouped into stations, exhibits, workplaces, etc. You can define the categories yourself. These are further grouped into departments, departments into floors, and floors into buildings.
In this way, buildings, floors or departments can be addressed in no time at all.
As a conclusion one can summarize:
Everything can be integrated into NeuroomNet as a component, be it a device, software or something else.
This ensures maximum flexibility when replicating the installation digitally.
The components can be grouped and nested as required. This keeps the system clear and intuitive.
The groups are easier to address and control.