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
oBIX and other Web Service Interfaces for IoT
- oBIX 1.1 interface supporting HTTP binding and XML encoding
- Supports HTTPS (TLS 1.2) and HTTP basic authentication
- Support for oBIX watches
- Conform to KNX Web Services which provides the possibility to use the NETx BMS Server as a standard conform KNX Web Service gateway
Interfaces to the field-/automation level
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 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
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 systems
MICROS Fidelio/Opera – 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
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. For MICROS Opera PMS V5 or higher, MICROS-Fidelio Suite 8.8 or higher, Fidelio FO 6.20, Fidelio Suite 7.13
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 systems
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.
All 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, …
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.
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).
HTTP Server and other Web Service Gateways – For integration of web content from HTTP servers; NETx BMS Server acts as HTTP client
Additional interfaces via hardware gateways – DALI, DMX, EnOcean, M-Bus
Your own interface – Via LUA scripting and C# .NET API
Customer specific interfaces – On request