{"id":9797,"date":"2026-08-06T18:18:47","date_gmt":"2026-08-06T10:18:47","guid":{"rendered":"https:\/\/blog.facilitybot.co\/?p=9797"},"modified":"2026-08-06T18:18:47","modified_gmt":"2026-08-06T10:18:47","slug":"how-to-connect-building-automation-systems-bas-to-a-cmms","status":"publish","type":"post","link":"https:\/\/facilitybot.co\/resources\/blog\/how-to-connect-building-automation-systems-bas-to-a-cmms\/","title":{"rendered":"How to Connect Building Automation Systems (BAS) to a CMMS"},"content":{"rendered":"

Your building automation system already knows when something is wrong. A chiller pulling too much amperage, an AHU running hot, a fire panel throwing a fault at 2 a.m., the BAS sees all of it in real time. The problem is what happens next. In most facilities, that alarm sits on an operator workstation until someone happens to notice it, decides it’s worth acting on, and manually types up a work order in a completely separate system.<\/p>\n

BAS CMMS integration closes that gap. When you connect BMS to CMMS, building performance data flows directly into your maintenance workflow, so alarms become prioritized work orders in minutes instead of hours. This guide walks through why that connection matters, the protocols and architectures involved, and a step-by-step process for setting it up.<\/p>\n

Why BAS and CMMS Need to Work Together<\/h2>\n

A building automation system and a CMMS are built to do different jobs. The BAS monitors and controls HVAC, lighting, fire systems, and other mechanical equipment, collecting thousands of data points an hour. The CMMS manages the human side of maintenance: work orders, technician assignments, parts, and history.<\/p>\n

Left disconnected, the handoff between “something is wrong” and “someone is fixing it” depends entirely on a person noticing the alarm and manually creating a ticket. That gap is where facilities teams lose the most time. Industry research on facilities operations consistently points to reactive maintenance eating up a large share of a maintenance team’s week, much of which could be avoided if building data triggered maintenance action automatically.<\/p>\n

\n\n\n\n\n\n\n\n\n
Impact area<\/th>\nWithout integration<\/th>\nWith integration<\/th>\n<\/tr>\n<\/thead>\n
Alarm response time<\/td>\nHours (next shift reviews logs)<\/td>\nMinutes (auto-generated work order)<\/td>\n<\/tr>\n
Energy waste detection<\/td>\nDays to weeks<\/td>\nSame-day<\/td>\n<\/tr>\n
PM scheduling<\/td>\nCalendar-based, fixed intervals<\/td>\nRuntime-based, matched to actual usage<\/td>\n<\/tr>\n
Compliance reporting<\/td>\nManual log compilation<\/td>\nCombined, largely automated<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

The Protocols Behind a BAS-CMMS Connection<\/h2>\n

Before you connect BMS to CMMS, it helps to know which language your building speaks. Three protocols cover the vast majority of buildings:<\/p>\n

BACnet.<\/strong> Developed by ASHRAE and published as an ANSI standard, BACnet is the closest thing building automation has to a universal language. It’s object-oriented, meaning every data point (a temperature sensor, an alarm, a schedule) is a defined object with standard properties, which makes it straightforward for a CMMS to interpret. BACnet also has native alarm and event notification, so your CMMS can subscribe to specific alarm types instead of constantly polling for changes.<\/p>\n

\"\"<\/p>\n

Modbus.<\/strong> Older and simpler than BACnet, Modbus is still common on standalone equipment like boilers, chillers, and submeters. It’s register-based, so your integration needs a register map, and it has no built-in alarming; your integration layer has to poll and compare values against thresholds itself.<\/p>\n

LonWorks.<\/strong> A peer-to-peer protocol popular in older and European buildings, LonWorks usually needs a dedicated gateway to translate into BACnet or a web API before a modern CMMS can use it.<\/p>\n

Three Ways to Connect BMS to CMMS<\/h2>\n

There isn’t one universal path for BAS CMMS integration. The right approach depends on your BAS age, protocol, and how many buildings you’re managing.<\/p>\n

1. API-based integration.<\/strong> Your BAS head-end (Niagara, Honeywell EBI, Siemens Desigo CC, Johnson Controls Metasys, and similar platforms) exposes data through a REST API, and your CMMS consumes it directly. This is usually the fastest and cheapest route for a modern, single-vendor BAS, and it works well with cloud-based CMMS platforms since it typically only needs outbound HTTPS.<\/p>\n

2. Middleware.<\/strong> For portfolios running multiple BAS vendors across different sites, a middleware layer (Niagara, SkySpark, CopperTree, or a custom pipeline) sits between the BAS systems and the CMMS, translating and normalizing everything into one feed. It handles complexity well but adds another platform to license and maintain.<\/p>\n

3. Direct or IoT-native integration.<\/strong> Some CMMS platforms speak BAS protocols natively, or use lightweight edge gateways, so alarm data flows straight into the same system that manages work orders and assets. Fewer moving parts, lower latency, but it depends on your CMMS having that native capability.<\/p>\n

\n\n\n\n\n\n\n\n
Factor<\/th>\nAPI-based<\/th>\nMiddleware<\/th>\nDirect\/IoT-native<\/th>\n<\/tr>\n<\/thead>\n
Typical setup time<\/td>\n4 to 8 weeks<\/td>\n8 to 14 weeks<\/td>\n3 to 6 weeks<\/td>\n<\/tr>\n
Ongoing maintenance<\/td>\nLow<\/td>\nMedium to high<\/td>\nLow<\/td>\n<\/tr>\n
Best for<\/td>\nSingle-vendor modern BAS<\/td>\nMulti-vendor portfolios<\/td>\nBuildings with a native-IoT CMMS<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

What Automated Work Order Generation Looks Like<\/h2>\n

This is the core use case that makes BAS CMMS integration worth the effort. Here’s the typical flow:<\/p>\n

    \n
  1. The BAS detects a fault, for example an AHU supply air temperature exceeding setpoint for a sustained period.<\/li>\n
  2. The alarm is sent to the CMMS through an API webhook or direct integration.<\/li>\n
  3. The CMMS auto-creates a work order with the asset ID, location, alarm details, and recent trend data.<\/li>\n
  4. The system assigns priority and routes the ticket to the right technician based on skills and availability.<\/li>\n
  5. The technician gets a mobile notification and responds, often with the relevant history already attached.<\/li>\n<\/ol>\n

    Facilities teams that put this in place typically see alarm-to-response time drop from hours to minutes, along with fewer emergency callouts, because problems get caught before they escalate.<\/p>\n

    Other High-Value Use Cases<\/h2>\n