Building management software 
for medium-sized and enterprise building automation projects

NETx BMS Server, OPC Server for KNX, BACnet, Modbus, SNMP, etc.

The NETx BMS Server is a flexible and scalable solution for the use of different systems and technologies. As a server application, it has the task to collect and process data points from building automation systems. Open technologies (e.g. OPC, KNX, BACnet, Modbus, SNMP, ...) and application-specific systems (MICROS Fidelio/Opera, Protel, VingCard, Kaba, Salto, ...) can be integrated as well as any amount of NETx Clients (NETx BMS Clients, NETx Voyager or NETx Shutter Control). Additionally, the NETx BMS Server includes a web server. This embedded web server offers the opportunity to create web based visualizations that can be displayed at any devices (incl. touch-able). Due to its features, the NETx BMS Server is an innovative solution for all requirements of modern building automation projects. 

Integration via OPC/BACnet
The NETx BMS Server includes an OPC interface,  which you can use to integrate data from other OPC servers but also third-party OPC clients. Using the BACnet interface of the NETx BMS Server connecting to other central building control systems like Siemens, Schneider Electric or Honeywell is possible.

Easy data import
For a comfortable and effective realization of your building automation projects several tools like the NETx BMS App are available. Using this app you can for example integrate data from the ETS of the KNX Association in the NETx BMS Server.  You can use the BACnet Explorer to discover BACnet divises and objects automatically without needing any extern tools.

Increasing efficiency
Each system technology like KNX or BACnet offers isolated functions and specific advantages. If a building automation system can combine the different system technologies, a significant additional value arises. For example, you can use the information of presence detectors to control illumination also for regulation of HVAC.  By this, existing resources are applied efficiently.
Server for OPC, KNX, BACnet, Modbus and SNMP. Interfaces to MICROS Fidelio, Opera, Protel, VingCard and Gira HomeServer. Integration of BACnet and OPC Clients possible.

Functions

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.

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.
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.
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.

 

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.

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.
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. 

 

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.
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

Interfaces to the management level

OPC
  • OPC DA 2.0 and OPC UA interface for OPC clients of third party manufacturers, e.g. third party visualizations
BACnet
  • BACnet/IP server interface for BACnet clients of third party manufacturers
  • Mapping of various data points (e.g. KNX, Modbus, SNMP, MICROS Fidelio/Opera, VingCard, ...) to BACnet objects
  • Supports COV subscription
  • Automatic or manual selection of object types
  • Configuration of read/write or read-only access possible
VNET
  • Reliable interface for all NETx Clients
  • Eases the firewall configuration
  • No Windows DCOM needed
Web-Interfaces
  • HTTP interfaces for NETx BMS Clients
  • Supports HTTPS
  • HTML5 and JavaScript for standard web browsers

Interfaces to the field-/automation level

KNX
  • Simple import from the ETS with the NETx BMS App
    • Import of all group addresses + automatic assignment to KNXnet/IP routers and interfaces
    • Recognizing of IP addresses of KNXnet/IP routers and interfaces
    • Import of all ETS views (building and trade view, topology including devices, communication objects and their data points)
  • Support of all standardized KNX data points
  • Non-standardized DPTs can be added
  • Uses KNXnet/IP tunnelling protocol: any KNXnet/IP router and/or interface can be used
  • Supports ABB IGS and eibNode
BACnet
  • Uses BACnet/IP protocol to integrate any BACnet/IP device
  • Other BACnet media (e.g. BACnet MS/TP devices) can be included via BACnet/IP routers
  • BACnet Explorer for automatic device and object discovery without the needed for external tools
  • Multiple BACnet priorities can be used at the same time
  • Supports confirmed/unconfirmed COV subscription, unsolicited COV notification and device polling
  • Supports BBMD
  • Supports proprietary BACnet objects
  • More information see BACnet PIC statement
Modbus
  • Supports Modbus/TCP protocol for the integration of Modbus/TCP devices
  • Supports Modbus/RTU via Modbus/TCP gateways or via simple IP-to-RS485 converters (native Modbus/RTU via TCP or UDP)
  • Manufacturer-specific configuration possible
SNMP
  • Support for SNMP v1, v2 and v3
  • Polling of SNMP objects via their OIDs
  • Writing of SNMP objects
  • Supports SNMP traps
  • SNMP device monitoring
OPC
  • OPC DA interface for the integration of data points of third party OPC DA servers e.g. fire alarm systems
  • Cluster Explorer for a simple import
  • Central aggregation of data out of different sub servers into the NETx BMS Server
Hotel management system MICROS Fidelio/Opera
The NETx BMS Server allows the combination of data from different systems e.g. hotel management and door lock systems. Therefore respectable potential savings can be realized. Using the check in / check out information from the hotel management system the HVAC system of a hotel room can be controlled. You can use the check in signal to controll the air-conditioning of the booked room or start the comfort mode. On the other hand the check out signal can be used to deaktivate the HVAC system or change to standby mode.

 

  • Certified interface, with the following functions:
    • Guest In/Out/GuestDataChange with Room move
    • Guest Message handling online/on request
    • Room Equipment/Room maid status/Do not Disturb
  • For MICROS Opera PMS V5 or higher, MICROS-Fidelio Suite 8.8 or higher, Fidelio FO 6.20, Fidelio Suite 7.13

 

 

Hotel management system Protel
Additonally to the MICROS Fidelio/Opera interface a Protel interface is available for the NETx BMS Server. This interface allows an exchange of information between the Server and Protel.
Door lock system VingCard

The NETx BMS Server is able to connect to the VisiOnline Server Software. The following events can be retrieved:

 

  • Guest entrance (including the card number)
  • Staff entrance
  • Inside open
  • Deadbolt thrown
  • Deadbolt released
 

Alle events are available as data points in the NETx BMS Server and can be further processed with other technologies like KNX, BACnet, Modbus, SNMP, MICROS Fidelio/Opera, ...

Door lock system Kaba
Kaba door locks are using a wireless communication protocol which is based on ZigBee. In order to retrieve information like door events, ZigBee/IP hubs are required. These hubs are provided by Kaba and have the aim to translate ZigBee packet into IP packets for the local area network (LAN). Depending on the project multiple ZigBee hubs are needed.

 

The events are centrally collected by the Kaba server software. This software package provides an interface called Messenger LENS web service interface. This interface provides the opportunity to send events via push notification to third-party software. This means that the Kaba software (web service client) sends web service requests to our NETx BMS Server (web service server). The interface itself uses SOAP based web services.
Door lock system Salto
Salto door locks are using a wireless communication protocol which is based on ZigBee. In order to retrieve information like door events, ZigBee/IP gateways are required. These gateways are provided by Salto and have the aim to translate ZigBee packet into IP packets for the local area network (LAN). Depending on the project multiple ZigBee gateways are needed.

The events are centrally collected by the Salto server software. This software package provides an interface called Salto Event Stream. This interface provides the opportunity to send events via push notification to third-party software. This means that the Salto software (TCP client) which sends TCP/IP packets to our NETx BMS Server (TCP server).
Gira HomeServer/FacilityServer
Additional interfaces via hardware gateways
  • DALI
  • DMX
  • EnOcean
  • M-Bus
Your own interface
  • Via LUA scripting
  • Via C# .NET API
Customer specific interfaces
On request

 

 

 

BMS Server Studio Studio XLogic EditorXLogic Editor

 ETS App

ETSApp

   

 

 

BMS Server Studio Studio

XLogic EditorXLogic Editor

 ETS App
ScreenshotETSAppneu

License types

Server license 
STARTER Max. data points: 250 / BMS Client licences: 1 Product-ID: S06.02.0.00.01
HOME Max. data points: 1,000 / BMS Client licences: 3 Product-ID: S06.02.0.00.02
BASIC Max. data points: 2,500 / BMS Client licences: 5 Product-ID: S06.02.0.00.03
PROFESSIONAL
Max. data points: 10,000 / BMS Client licences: 10 Product-ID: S06.02.0.00.04
ENTERPRISE Max. data points: 25,000 / BMS Client licences: 10 Product-ID: S06.02.0.00.05
CUSTOMIZED Max. data points: variable / BMS Client licences: > 10 Product-ID: S06.02.0.00.06
Add. BMS Client   Product-ID: S08.01.0.01.01
 
Interfaces
MICROS Fidelio/Opera   Product-ID: E03.03.5.01.00
Protel   Product-ID: E06.02.0.00.03
VingCard 5 data points per door lock Product-ID: E06.02.0.02.02
Kaba 5 data points per door lock Product-ID: E06.02.0.02.05
Salto 5 data points per door lock Product-ID: E06.02.0.02.04
Gira HomeServer / FacilityServer Not charged seperately - licensed according to number of used data points in BMS Server Product-ID: E06.02.0.02.00

 


To support you in the realisation of your projects we offer selected server hardware. Each server is delivered with already installed software. So, you can save the time for hardware search and get a perfect concerted package of hard and software. 

Please contact us for an individual offer. We would be glad to advise you about the possibilities for your project.

download Software  |  Documentation |  Product data sheet Request

 

 

 

 

System requirements:

PC: Intel or AMD - 1.8 GHz (multi-core recommended), 4GB RAM, Hard disk: 16 GB (32 GB recommended), Ethernet interface: 100 MBit/s
Operation system: Windows 7 - SP 1 (32 bit | 64 bit), Windows 8 (64 bit) | Windows 8.1 (64 bit), Windows 10, Windows Server 2008 R2 (32 bit | 64 bit), Windows Server 2012 | 2012 R2 (64 bit)