How PEAK connects to your building
PEAK integrates with any building management system that exposes BACnet/IP, routed BACnet MS/TP, a vendor API or scheduled CSV exports, without a rip-and-replace of your existing controls.
PEAK only reads. It does not command plant, does not alter your control strategy, and requires no new field devices. The only hardware on site is the BACER collector, which reads the network.
Four ways PEAK reads your BMS
PEAK is BMS-agnostic. It reads your existing building management system, meters and sub-meters, then analyses that data independently of the system that produced it. Every site connects through one of these four paths.
BACnet/IP
The BACER collector reads BACnet/IP traffic directly on the BMS network. Highest fidelity and lowest lag. Used at any site where BACnet/IP is exposed.
BACnet MS/TP routed to IP
MS/TP trunks are routed to BACnet/IP through a BACnet router, and BACER reads the IP side. Routers commonly already in place include the Tridium JACE, Johnson Controls SBH, Contemporary Controls BASrouter and Delta eBMGR.
Vendor API
BACER reads the BMS through the vendor's API. Used where BACnet/IP cannot be exposed and MS/TP routing is not practical.
Scheduled CSV extract
The BMS or EMS server sends scheduled exports on a timetable. Lower fidelity, fewer points and more lag than the live paths, so it is used only where no live path is available.
Which path suits your site
| Path | Live data | BACER on site | Best for |
|---|---|---|---|
| BACnet/IP | Yes | Yes | Sites already exposing BACnet/IP |
| BACnet MS/TP routed to IP | Yes | Yes | Estates running MS/TP on the controller side |
| Vendor API | Yes | Yes | Where BACnet cannot be exposed |
| Scheduled CSV extract | No | Typically not required | Sites with no live path available |
Live paths deliver higher fidelity and lower lag than scheduled extracts, which is why CSV is used only where no live path is available.
What is BACnet, and why it matters
BACnet (Building Automation and Control networks) is the data communication protocol developed by ASHRAE to let building automation devices from different manufacturers talk to each other. It is the most widely deployed building communication protocol in the world, with global market share above 60%.
BACnet/IP
Runs over the IP network. PEAK reads this directly, with no hardware on site beyond the BACER collector.
BACnet MS/TP
Runs over RS-485 serial, typically between field controllers. It needs routing to BACnet/IP before PEAK can read it, and most estates already have a router doing this.
A system described as BACnet compatible may be running MS/TP only, so it is worth confirming which form is in use before assuming an integration path. Where a BMS network spans several IP subnets or VLANs, PEAK works with whichever arrangement the site already has: an existing BBMD forwarding broadcasts between subnets, BACER registered as a foreign device, or BACER placed on the same subnet as the devices it reads.
Beyond the BMS
The BMS is one source. PEAK consolidates everything the building already produces into a single portfolio dataset.
Meters and sub-meters
Electricity, gas and water feeds, including interval and sub-meter data.
IoT sensors
Temperature, humidity and equipment sensors already installed on site.
Lifts and plant
Lift controllers, HVAC plant and other equipment feeds available on the network.
Weather data
Local conditions used to normalise performance and separate weather effects from faults.
PEAK runs across more than 600 commercial buildings in 11 countries and four continents, with the largest deployments in the United States, the United Kingdom, Ireland, Australia and New Zealand.
Building management systems PEAK reads
PEAK connects to the systems already installed across commercial estates. The list below covers platforms connected in production today.
Trend
Tridium Niagara
Schneider Electric
Honeywell
Siemens
Johnson Controls
Distech Controls
Delta Controls
Alerton
Automated Logic
Where your BMS data goes next
Connecting the data is step one. These are the outcomes it feeds.
Fault detection and diagnostics
How PEAK detects, prioritises, assigns and verifies equipment faults across any BMS.
Retro-commissioning
Deliver RCx projects faster and keep clients after handover, across any BMS.
Data-driven maintenance
Stop servicing equipment that is fine, and hold contractors to an independent record.
BMS vs PEAK
How a building analytics platform differs from the BMS it sits alongside.
Order a BACER
Request the edge collector that reads your building network.
Security
How CIM secures building data: SOC 2 framework, encryption and access controls.
BACnet is an ASHRAE standard (ANSI/ASHRAE Standard 135). Further detail on the protocol and its deployment is published by BACnet International and ASHRAE.
Frequently asked questions
Common questions about connecting PEAK to an existing building management system
No. PEAK reads data from your existing BMS and analyses it. It does not control plant, does not change your control strategy, and does not require any part of your controls to be replaced.
PEAK is vendor-agnostic. Rather than supporting a fixed list of brands, it connects through BACnet/IP, routed BACnet MS/TP, vendor APIs or scheduled CSV extracts, which covers the large majority of commercial building management systems in use today.
No. PEAK uses the data your BMS, meters and sub-meters already produce. The only hardware on site is the BACER collector, which reads the network.
Yes, once the MS/TP trunks are routed to BACnet/IP. Many estates already have a suitable router in place. Where one is not installed, adding it is normally a BMS contractor task rather than an IT change.
Confirm which integration path the site supports, make BACnet/IP visible to the BACER install point, and confirm device IDs and network numbers are unique across the network. Full contractor guidance is on the PEAK Help Centre.
Still have questions?
Can’t find the answer you’re looking for? Please check our support page or chat to our friendly team.
