Priva

Role in our panels

How we use Priva

The Priva Blue ID controller is the core field device in Priva's building automation range. Available with 36 universal I/O points (configurable as analog input, analog output, digital input, or digital output), the Blue ID communicates on a BACnet/IP LAN network and supports BACnet MS/TP for local field bus connections (actuators, sensors). The Blue ID is programmed using Priva's Flexbuilder engineering tool — a graphical programming environment with pre-built HVAC sequences (VAV, CAV, fan coil, heat pump, chilled beam). The controller handles PI control loops, schedules, and alarm management locally without requiring constant server connectivity. The Blue ID KNX Card is Priva's native KNX integration module for the Blue ID controller. The ETS6 application for the Blue ID KNX Card is downloaded from the Priva Support Portal (priva.com/support). After importing the ETS application into ETS6, the installer configures the Blue ID IP address and selects which BACnet data points to expose as KNX group objects. All tagged BACnet Analog Inputs, Analog Outputs, Binary Values, and Binary Outputs appear as group objects with automatically assigned DPTs. Bidirectional operation: a KNX room thermostat sends measured temperature (DPT 9.001) to a KNX GA → Blue ID KNX Card writes this value to a BACnet Analog Input → Priva heating/cooling PI loop uses this as the measured temperature variable. Conversely, Priva Blue ID calculates valve position (0-100%) → BACnet Analog Output → KNX GA → KNX switching actuator → physical zone valve. Connext is Priva's web-based BMS server platform, replacing the earlier Priva Building Operator (PBO). Connext communicates with Blue ID controllers via BACnet/IP and provides a modern HTML5 dashboard interface accessible from any browser. Connext includes an OPC UA server (port 4840) — the Lingg and Janke KNX Virtual OPC UA Client connects to Connext OPC UA and makes all BACnet data points available as KNX group addresses in ETS6 Virtual. This path is used for supervisory-level BMS integration where real-time bidirectional control is not required (trend logging, setpoint scheduling, energy dashboards). A representative Dutch institutional use case: hospital with 12 floors, each floor having 20 patient rooms. Each floor has one Blue ID with KNX Card controlling fan coil units (Priva HVAC logic) and KNX group addresses for the KNX lighting actuators and pushbutton panels in patient rooms. Connext BMS at hospital level provides ward-by-ward setpoint scheduling, alarm management, and energy monitoring. The ARISTO BewO energy management system receives OPC UA data from Connext for M&T reporting required by Dutch healthcare facility regulations.

Priva Blue ID has an optional KNX module (Blue ID KNX Card) providing native KNXnet/IP integration. ETS6: download Priva ETS application from Priva Support Portal → configure IP address → all BACnet data points tagged for KNX appear as group objects. Bidirectional: KNX room thermostat temperature (DPT 9.001) writes to Priva Blue ID BACnet Analog Input → Priva uses measured value in heating/cooling PI loop. Priva BACnet Binary Output (valve position) writes back to KNX switching actuator → physical valve. Connext BMS: OPC UA Server on port 4840 → Lingg and Janke KNX Virtual OPC UA Client → bidirectional for supervisory control.