KNX

• Simple import from the ETS with the NETx BMS App Secure
  • 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 KNX IP Security standard
• 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
• KNXnet/IP routing available

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 interface for the integration of data points of third party OPC 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 Platform

MQTT

• MQTT interface to communicate with one or more MQTT brokers
• Support of TLS security
• Publishing/subscribing to MQTT topics

Hotel management systems

Oracle Fidelio/Opera

• Guest In/Out/GuestDataChange with room change
• Guest Message handling online/on request
• Room Equipment/Room maid status/Do not Disturb

The NETx BMS Platform 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 booked rooms or start the comfort mode. On the other hand the check out signal can be used to deactivate the HVAC system or change to standby mode. For Opera PMS V5 or higher, Fidelio Suite 8.8 or higher, Fidelio FO 6.20, Fidelio Suite 7.13

Infor

Infor Hospitality Management Solution (HMS ™) - cloud-based hotel management system

Protel

Additonally to the Fidelio/Opera interface a Protel interface is available for the NETx BMS Platform. This interface allows an exchange of information between the Server and Protel.

Door lock systems

VingCard

The NETx BMS Platform 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.
All events are available as data points in the NETx BMS Platform and can be further processed with other technologies like KNX, BACnet, Modbus, SNMP, Fidelio/Opera, ...

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 packets 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 Platform (web service server). The interface itself uses SOAP based web services.

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 packets 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) sends TCP/IP packets to our NETx BMS Platform (TCP server).