This Website is using cookies to improve your user experience and our service. By using this website you agree the use of cookies.

  1 Integration of different protocols and technologies

  2 Trending

  3 Configuration and monitoring

  4 Scheduler - Server calendar

  5 Web visualization

  6 Adding extended functions

  7 Smart metering

  8 Main/Backup

  9 Clustering

10 Extension Manager

 

 

Integration of different protocols and technologies

Numerous opportunities of integration - With the NETx BMS Server, many different protocols and technologies can be integrated. Besides KNX, BACnet, Modbus, OPC and SNMP, additional interfaces for application specific systems like MICROS Fidelio/Opera, Protel or VingCard are available. Via hardware gateways DALI, M-Bus, EnOcean or DMX can be integrated. The modular structure of the NETx BMS Server enables you to integrate additional interfaces via the embedded script engine or via a C# .NET API. On request, also project specific interfaces are possible.

Simple exchange of data - The NETx BMS Server acts as a multi-protocol gateway. Therefore, you can bidirectionally exchange data and information between different protocols and technologies. If the exchanged data varies concerning type, automatic conversion rules are applied. By using the integrated logic engine, also a  manual conversion can be effected.

 

Trending

The NETx BMS Server contains an SQL database as default. So you can record and archive all changes of selected data points. Besides data point values, important meta-information like timestamp or the source of the data change (address of device and/or client, visualization user, ...) are stored.

 

3  Configuration and monitoring
The NETx BMS Server is a server application, running as Windows system service or Windows server application. Configuration and maintenance are done within the NETx BMS Server Studio. The NETx BMS Server Studio is a graphical user interface for performing different management tasks. In the "Server Item Tree“, you can view and change data points, their values and properties in real time. This view is identical to the one a management client has to the data points of the NETx BMS Server. With the integrated telegram monitor, network traffic can be monitored. Also, the monitoring of connected clients is possible. The studio has different additional tools, e.g. for the simple import of ETS projects. By using the BACnet Explorer, BACnet devices and their objects can be discovered and imported automatically. The Cluster Explorer provides the opportunity to search for data points in third party OPC servers.

 

4  Scheduler - Server calendar
With the server calendar of the NETx BMS Server, time based events can be defined. According to the start and end time of an event, data points are changed and time based events are triggered - independent of the underlying technology. In addition, the calendar functionality allows to define periodic events.

 

5  Web visualization
Through the integrated web server, you have access to web based high-end visualizations. These visualizations are created with the NETx BMS Client Editor. Management, analysis and updating of the visualization clients are done centralized. The web server only uses HTML and JavaScript. Therefore, the clients require a standard web browser - no additional plug-ins or add-ons. A detailed description for the NETx BMS Clients can be found here.

 

6  Adding extended functions
If the available control functions of the field and automation level are not sufficient, you can add missing functionalities by server tasks, timers or virtual links. In addition to the LUA script engine, the NETx BMS Server contains the XLogic Editor. Using this graphical editor, you can implement control logic (XCommands) and add control functions to the building automation system. XCommands access the functions of the NETx BMS Server and process the available data of the server. The following functions are possible:

  • reading and writing data points
  • performing mathematical operations and calculations
  • sending e mails
  • retrieving the server status
  • invoking LUA functions

To ease the development of your own control logics, ready for use logic functions are included. In addition, virtual data points can be created to define user specific virtual structures. These data points are only existing in the server and can be used in the same way as physical data points.

 

7  Smart metering
The NETx BMS Server contains a metering module. This module measures the consumption values of the smart meters. Afterwards, you can visualize these values with the NETx BMS Clients or the NETx Voyager. Additionally, the MaRS Module is available. Based on a hierarchically organized cost centre structure, extensive consumption and cost calculations can be done. These calculations are possible for a single meter, a dedicated cost centre or a combination of them. The results can be shown as a diagram, graph or table.

 

8  Main/Backup
Use of Main/Backup gives higher security
Building automation systems have to be reliable. Therefore, you have the opportunity to integrate the NETx BMS Server as a main/backup solution. In this case, the management clients can communicate with the main and the backup server. If the communication to the main server is interrupted, the connection to the backup server is activated automatically and the data can further be retrieved from the building automation system. This switch is done automatically - without any interruption of the application (e.g. visualization). 
You do not need to be offline to do maintenance work at your system 
A main/backup solution does not only increase the reliability of the system, but also eases the maintenance work. If you have to change the configuration of the building automation system online, simply switch off the main server to do the necessary tasks. The backup server will be online during this maintenance period and the management clients can be used as usual. Switching between main and backup server is done automatically - your action is not required.

 

9  Clustering
By using the Cluster module of the NETx BMS Server, data points of other NETx BMS Servers can be integrated. Clustering enables you to exchange data point values and to distribute the load between different NETx BMS Servers. Using this concept, you can create a hierarchy of NETx BMS Servers. This is suitable for projects, which consist of several buildings, connected through a Wide Area Network (WAN). Each building has its own NETx BMS Server, operating as a sub server for the whole building. To get a global overview over all buildings (e.g. in a master visualization), you can interconnect these sub servers by a central NETx BMS Server. The advantage is that all sub servers can operate independently, while the central server collects information of all buildings. Due to the reliable connection between main and the sub servers, they can be on different geographic positions. To guarantee highest redundancy, the clustering can also be combined with a main/backup solution.

 

10  Extension Manager
The NETx BMS Server supports not only a multitude of systems and technologies, several extension modules are available, too. To be more flexible the BMS Server includes a tool called Extension Manager. Using an online repository, the Extension Manager provides the possibility to install and/or update drivers and modules on demand -- without the need to update the core of the NETx BMS Server. Currently, the following extensions are available:

  • Salto plugin: allows the integration of online Salto door locks.
  • Kaba plugin: allows the integration of online Kaba door locks.
  • Support tool plugin: provides different modules for simplifying BMS Server diagnostic (memory profiler, network sniffer)
  • OPC UA

System requirements

PC: Intel or AMD - 1.8 GHz (multi-core recommended), 4GB RAM, Hard disk: 32 GB (64 GB recommended), Ethernet interface: 100 MBit/s
Operation system: For maintainable systems we strongly recommend at least Windows 10 or Windows Server 2016 (or higher), except NETx KNX OPC Server 3.5. Our products basically also run on older Windows versions down to Windows 7 and Windows Server 2008. However, due to limited future support for these operating systems by Microsoft we will not be able to provide full support for our software running on these systems.