Deployment Concern

Building Automation Compatibility

The short version: ClimaMind connects through approved BAS/BMS protocol paths and works with common building automation platforms without replacing the existing BAS/BMS.

No rip-and-replace: the BAS/BMS remains the site operator interface and local control layer. ClimaMind uses the approved interface exposed by the customer, SI, or BMS contractor.

Protocols

Supported protocols

We currently support BACnet/IP, Modbus TCP, Modbus RTU, OPC UA, Snap7, HTTP, and MQTT for BAS/BMS integration.

BACnet/IP

Typical use: BAS object access for schedules, trends, values, and supervisory points.
Integration path: Primary path for mature commercial BAS/BMS networks.

Modbus TCP

Typical use: Meters and equipment controllers on IP networks.
Integration path: Common for plant meters, chillers, pumps, and gateway devices.

Modbus RTU

Typical use: Meters and equipment controllers on serial networks.
Integration path: Usually connected through an edge gateway or BAS integration panel.

OPC UA

Typical use: Industrial, SCADA, PLC, and enterprise gateway data surfaces.
Integration path: Useful when a site exposes a structured server instead of direct BAS objects.

Snap7

Typical use: Siemens PLC paths when HVAC or plant signals are exposed through S7-compatible access.
Integration path: Project-specific PLC tag mapping with the customer or SI.

HTTP

Typical use: Approved REST-like gateway, historian, or middleware endpoints.
Integration path: Used when the site already exposes a controlled API boundary.

MQTT

Typical use: Gateway-published telemetry and event streams.
Integration path: Useful for edge gateways, brokers, and normalized telemetry feeds.

Platforms

Compatible BAS/BMS platforms

These platform names are practical starting points, not blanket certification. Fit still depends on site access, point mapping, write permission, and SI or BMS contractor support.

Vendor	Platform	Fit notes
Tridium	Niagara	Primary integration layer; commonly used to expose multi-vendor BAS points.
Schneider Electric	EcoStruxure	Mainstream open BMS path for trends, live points, and approved supervisory writes.
Johnson Controls	Metasys	Common large-building BMS; confirm objects, priority array, and permissions.
Siemens	Desigo CC	Common campus and large-building platform; access depends on site tooling and permissions.
Honeywell	WEBs	Niagara-based path when the station, drivers, and writable objects are available.
Distech Controls	EC-Net	Niagara-powered environment with strong open-protocol integration potential.
Lynxspring	JENEsys	Niagara-based edge and supervisor path; confirm station access and drivers.
Automated Logic	WebCTRL	BACnet-oriented BMS; third-party write permission must be confirmed.
Carrier	i-Vu	BACnet-oriented path for Carrier and mixed equipment sites.
Delta Controls	enteliWEB	BACnet-native environment; confirm exposed objects and control boundaries.
Trane	Tracer	Open-standard integration path when site tools and application boundaries allow it.
ABB Cylon	ASPECT	BACnet and Modbus friendly BMS path; PLC-style sites require more mapping.
J2 Innovations	FIN	Semantic integration layer; useful when the site exposes usable points and permissions.

Back to deployment overview