PEAK compatibility depends on two things: BMS data access (this article) and site network access (see Site Network and IT Requirements). Both need to be confirmed before committing hardware. Some readers, particularly where the BMS contractor also manages IT, will need to work through both articles together.
Overview
PEAK reads BMS data via one of four paths. Confirm at least one is achievable at your site before committing hardware:
BACnet/IP native - BACER reads BACnet/IP traffic directly on the BMS network.
BACnet MS/TP routed to IP - MS/TP trunks are routed to BACnet/IP via a BACnet router; BACER reads the IP side.
API fallback - BACER reads the BMS via an accepted vendor API (currently via Tridium Niagara, Siemens Desigo, and Schneider Electric EcoStruxure).
CSV automated extraction - the BMS or EMS server sends scheduled CSV exports. A BACER is typically not required on site for this path.
If none of the four is achievable, contact your CIM representative before committing hardware.
What is BACnet
BACnet (Building Automation and Control networks) is a data communication protocol developed by ASHRAE. It standardises communication between building automation devices from different manufacturers and is the most widely deployed building communication protocol, with a global market share exceeding 60%.
BACnet exists in two forms relevant to PEAK:
BACnet/IP - BACnet messages over standard IP networks. BACER reads this directly.
BACnet MS/TP - BACnet messages over RS-485 serial, common between field controllers. BACER cannot read MS/TP directly; it must be routed to BACnet/IP first.
A common misread: a BMS described as "BACnet compatible" may be running MS/TP only. Always confirm which flavour is in use.
Path 1 - BACnet/IP (preferred)
Confirm:
BACnet/IP traffic is visible from the proposed BACER install point.
BACnet device IDs and network numbers are unique across the network.
The BACnet UDP port (typically 47808, sometimes configured differently per site) is not blocked between BACER and the BMS devices.
Path 2 - BACnet MS/TP routed to IP
Used when the BMS runs MS/TP on the controller side. Confirm:
MS/TP trunks are routed to the IP network via a BACnet router. Common examples include the Tridium JACE, Johnson Controls SBH, Contemporary Controls BASrouter, and Delta eBMGR.
If not currently routed, an MS/TP-to-IP router can be installed. This is usually a BMS contractor change, not an IT change.
Device IDs and network numbers remain unique across all routed networks after routing is added. Duplicates break BACnet discovery.
Multi-subnet networks (BBMD)
If the BMS network spans multiple IP subnets or VLANs, BACnet broadcasts will not cross between them without help. Confirm one of:
A BBMD (BACnet Broadcast Management Device) is already configured on the BMS network and will forward broadcasts between subnets, or
BACER can be registered as a Foreign Device in an existing BBMD's Broadcast Distribution Table, or
BACER can be placed on the same subnet as the BMS devices it needs to read, so no cross-subnet forwarding is required.
Path 3 - API fallback
Used when BACnet/IP cannot be exposed and MS/TP routing is not an option. The BMS platform must match one of:
Tridium Niagara via nHaystack. The nHaystack module must be installed (or available to install on the Niagara version in use) and reachable from another device on the network.
Siemens Desigo CC via the Desigo REST API. The API must be enabled, a licensed API user provisioned, and the endpoint reachable from a device other than the Desigo CC server.
Schneider Electric EcoStruxure via SmartConnector. SmartConnector must be installed and licensed on the EcoStruxure Building Operation server, with an integration user available.
Platforms outside this list are not currently supported via API. Contact your CIM representative before committing hardware.
Path 4 - CSV automated extraction
For sites that are not BACnet/IP compatible and do not have an accepted API, PEAK can ingest data via automated CSV extracts emailed from the BMS or EMS server on a schedule. A BACER on site is typically not required for this path; the BMS or EMS server handles the export and outbound delivery directly.
To confirm CSV compatibility, email the following to engineering@cim.io:
BMS or EMS vendor type (e.g. Optergy, Siemens Apogee, Schneider Electric, Resource Advisor).
A sample CSV including date/time, point name, and point value.
When your site is not compatible
Contact your CIM representative before committing hardware if any of the following apply:
The BMS is on a LON network with no BACnet/IP layer.
The site is BACnet MS/TP only, no router is installed, and the BMS contractor is unwilling to add one.
The BMS spans multiple IP subnets with no BBMD configured and no plan to install one.
The platform is not in the Path 3 API fallback list, BACnet/IP cannot be exposed, and CSV extraction is not available.