What should you know about Nexo architecture?
The Nexo application works excellently as a tool facilitating responsible management of thermal energy consumption, which is very important in the era of constantly changing prices. In previous publications, we have already presented selected Nexo possibilities, and you will soon find more articles on this topic on our blog. This time we want to focus on the architecture of this system rather than on Nexo’s capabilities.
What does Nexo look like from the back?
The two main building blocks of the Nexo architecture are the Nexo Cloud platform and the Nexo gateway. Through the platform, the user manages their end devices (e.g., thermostatic heads, electrical sockets, etc.). The gateway is a physical device allowing users to connect their end devices and communicate between them and the Nexo Cloud platform.
The end user does not have direct access to the Nexo gateway. It is not even necessary for him to know of its existence. For the end user, it is crucial to have access to a cloud platform that allows him to control and monitor their devices. All communication between the cloud platform and end devices is fully transparent for the user.
Depending on the size of the building, there may be one or many Nexo gates in a given location. A single Nexo gateway can support multiple Nexo nodes. The Nexo node is a virtual element of the system assigned to a specific user. We assume that a single node corresponds to a single apartment in a multi-family building and, in the case of office buildings – to a single room, i.e., open space, coffee room, or meeting room. This solution ensures the complete separation of devices installed on different premises.
Each user has access only to their nodes, which can be served by various Nexo gateways. It means that users cannot manage devices that are not their own. This approach does not require the installation of physical Nexo gates in the number corresponding to the number of serviced premises, which reduces the costs associated with the implementation and subsequent operation of the system. The user under his account can connect one or many nodes he has permission.
Microservices and databases
The operation of Nexo is determined not only by the architecture elements mentioned above but also by various microservices that provide additional functionalities following the client’s needs. An example of microservice Nexo is a module equipped with machine learning, which is used to analyze and predict various parameters of a single-user installation and the system operating in the building.
These parameters are all relevant data on the operation of devices and other information necessary from the customer’s perspective (for example, weather data for a given location). They are collected in databases. Based on the collected data, advanced visualizations are provided, which enable the control of the installation and the analysis of its operation. We mentioned the possibilities in this matter in previous entries.
Such an architecture Nexo model allows you to prepare a complete work environment adapted to the customer’s needs. However, it requires maintaining a dedicated cloud platform.
In subsequent articles, we will discuss our approaches to developing Nexo and models of its distribution. One of them is particularly attractive for those customers who don’t expect personalized solutions but, at the same time, they want to use them immediately. Which solution will be best for you? The answer is coming soon on our blog.