BAS System Integration

Building Automation System Integration

Bring HVAC equipment, packaged units, meters, IAQ sensors, VFDs, plants and lighting controls into one usable control environment — with a documented point map, not a black box.

BACnet/IP
BACnet MS/TP
Modbus RTU
Modbus TCP
Gateways
Point mapping

Discuss an Integration Project Request a Quote

Integration scope

What we integrate

HVAC equipment controls
Third-party packaged equipment
Meters and electrical data
Lighting controls where an interface is available
Indoor air quality sensors
VFDs
Boilers and chillers
VRF systems
DOAS equipment
Life-safety status points only where permitted and properly designed
Cloud and analytics platforms where supported
Legacy controls segments retained during a phased retrofit

The real question

“Can it be integrated?” is usually the wrong question

Almost anything can be integrated given enough gateways and enough money. The useful questions are narrower: what does this equipment actually expose, how reliable is that interface, what does it cost to maintain, and what will you do with the data once you have it.

A packaged rooftop unit with a native BACnet card exposing forty points is a different proposition from the same unit with three hardwired outputs. Both can be “integrated”. Only one gives you diagnostics.

We document what each piece of equipment offers before proposing an approach, and we are direct about the cases where the answer should be a few hardwired points rather than a gateway nobody will maintain.

Operator monitoring integrated building and supported security systems — Useful integration begins with defined ownership, supported interfaces and a clear operating purpose.

Controls technician commissioning building automation equipment in a mechanical room

Commercial facility operator reviewing building automation performance

Methods

How equipment gets connected

Native protocol interface

The equipment speaks BACnet or Modbus directly. Cleanest option — most points, fewest moving parts.

Manufacturer gateway

A vendor-supplied translator. Works well, but becomes a support dependency worth understanding before you commit.

Third-party protocol gateway

Useful for legacy or unusual equipment. We document the register map so the mapping is not lost with the installer.

Hardwired points

Start/stop, status, alarm and setpoint as physical I/O. Fewer points, but nothing to go obsolete.

Meter pulse or protocol

Electrical, gas and water metering brought in for trending and demand visibility.

API / cloud integration

Where a platform supports it and the owner authorizes the connection, data can move to analytics platforms.

Deliverables

What integration work should leave behind

An integration nobody documented is a liability the day the person who built it leaves.

Integration point map

Every integrated point traced to its source device, object identifier or register address, with units and scaling.

Device inventory

Make, model, firmware, address and physical location for each integrated device and gateway.

Network topology record

Trunk layout, device counts per segment, terminations and any repeaters or routers.

Interface documentation

The vendor protocol document or register map used, archived with the project file.

Failure behaviour

What the BAS does when an integrated device stops responding — and what alarm tells you.

Verification record

Each integrated point checked against the source system, not assumed correct because it populated.

Questions

Frequently asked questions

Usually yes, and this is the normal condition in commercial buildings rather than an unusual one. What varies is the depth of integration per manufacturer. Some equipment will give you full point-level visibility; some will give you start, stop, status and alarm. We map that out per unit so you know before pricing what you will actually see on each piece of equipment.

They are the same protocol over different physical networks. MS/TP runs over twisted-pair RS-485 in a daisy chain — inexpensive, well-suited to field controllers, but limited in speed and device count per segment. BACnet/IP runs over standard Ethernet — much faster and easier to extend, but it puts controls devices on a network your IT group cares about. Most buildings use both: IP for the backbone and supervisory devices, MS/TP for terminal-level controllers.

When it eliminates duplicated schedules, gives operators one place to look, or provides occupancy and runtime data you will use — yes. When the interface is fragile, the point count is expensive, or the only outcome is a status indicator nobody checks — no. We evaluate it per building rather than treating integration as automatically correct.

Often, depending on whether the platform requires manufacturer-specific programming software or licensed credentials to add points. This is the first thing we verify. If we cannot legitimately obtain the access needed, we say so rather than proposing a workaround that leaves you with an unsupportable system.

Next step

Have equipment that needs to be on one system?

Send us the equipment list with make and model where you have it. We will tell you what each unit can realistically expose and what integration method makes sense for it.