← SERVICES
BACNET

BACnet Integration & Multi-Protocol BAS Work

Real BACnet work — discovery, addressing, routing, and integration across BACnet/IP, MS/TP, and gateways for legacy or non-BACnet equipment.

BACnet/IPBACnet MS/TPBACnet/SCModbus → BACnetASHRAE Standard 135

BACnet (ASHRAE Standard 135, ISO 16484-5) is the dominant open protocol in building automation. In practice, though, "BACnet" hides a lot of complexity: BACnet/IP and BACnet MS/TP behave very differently on a network, vendor implementations vary in completeness, and integrating non-BACnet equipment requires gateway work and careful object mapping. Vertex specializes in real BACnet integration — the kind where you can hand us a building full of equipment from five manufacturers and we'll deliver one unified, properly addressed BACnet network with clean discovery, predictable routing, and documented objects.

WHAT WE DELIVER

BACnet/IP network design

Subnet planning, BBMD (BACnet Broadcast Management Device) configuration for routed networks, foreign device registration where needed, and Device Instance ID schemes that scale across buildings.

BACnet MS/TP trunk design

RS-485 trunk segmentation, MAC addressing, baud-rate decisions, biasing and termination, and tools-based troubleshooting when a trunk goes flaky.

Device discovery and object mapping

Whois/Iam discovery, manual device addressing where required, object property reads, and clean exposure of controlled equipment as BACnet objects to the supervisor.

Gateway integration for non-BACnet equipment

Modbus RTU/TCP-to-BACnet gateways for chillers, VFDs, meters, and generators. LON-to-BACnet for legacy installations. Custom point mapping and scaling documented per device.

BACnet/SC migration planning

BACnet/SC (Secure Connect) is the modern, TLS-secured transport. We plan and pilot BACnet/SC deployments where customer security requirements demand it.

Documentation that doesn't lie

Device Instance ID list, object naming conventions, MS/TP MAC map, network topology, and a maintained as-built BACnet point list per building.

HOW WE WORK

Five stages we run on every bacnet project — adjustable to your timeline, but never skipped.

01

Network audit and protocol plan

Walk the building, identify every device that does or should speak BACnet, document existing addressing chaos, and produce a target network design.

02

Addressing scheme and Device Instance IDs

Design a Device Instance ID scheme that's unique across the building and predictable to read. Plan MS/TP MAC addresses by trunk. Document everything before configuration begins.

03

Discovery and integration

Bring devices online segment by segment, validate discovery, verify every object reads true value, and bind the supervisor (Niagara or otherwise) to the discovered points.

04

Gateway work and exception handling

For non-BACnet equipment, set up gateways with point-by-point Modbus or LON-to-BACnet maps. Validate values against the equipment's native interface before going live.

05

Documentation and turnover

Deliver a complete BACnet network diagram, object list, gateway configuration backups, and a written operations playbook for the network.

STANDARDS WE WORK TO

  • ASHRAE Standard 135 (BACnet)
    The base BACnet protocol standard, currently in its 2024 edition.
  • ISO 16484-5
    The international standard mirror of BACnet 135.
  • ASHRAE Standard 135.1 (BTL)
    BACnet Testing Laboratories conformance standard, used to validate vendor compliance.
  • BACnet/SC (Secure Connect)
    The TLS-based secure transport for BACnet, designed for IP-routed and cloud-connected networks.

TYPICAL PROJECTS

Multi-vendor consolidation

Building with controls from Trane, Carrier, Daikin, and JCI — each with its own proprietary or partial BACnet implementation. We discover what we can, gateway what we have to, and present a single normalized BACnet network to the supervisor.

Modbus chiller plant integration

Chillers and pumps reporting Modbus only. We install Modbus-to-BACnet gateways, map every status, alarm, and setpoint to clean BACnet objects, and expose runtime data to the BAS for trending and optimization.

Generator and ATS integration

Generators and automatic transfer switches reporting via Modbus or proprietary protocols. We gateway them onto BACnet so emergency power status appears on the BAS alongside HVAC.

Submetering integration

Electrical, water, gas, and BTU meters speaking Modbus RTU on RS-485 trunks. We translate to BACnet, expose cumulative and demand values, and feed energy dashboards.

RELEVANT CASE STUDIES

FAQ

Common questions

Can you integrate a building with no BACnet at all?
Yes. If the controllers speak Modbus, LON, MQTT, or proprietary protocols, we bring them onto BACnet using gateways and document the point mapping. Customers end up with a single, open BACnet network even if the underlying equipment is mixed.
What's the difference between BACnet/IP and BACnet MS/TP, in practice?
BACnet/IP runs on standard Ethernet/IP — fast, easy to route, but the network needs proper BBMD configuration to handle broadcasts across subnets. BACnet MS/TP runs on RS-485 twisted pair — slower, but cheaper to deploy to many devices, and resilient to electrical interference if installed correctly.
Do you do BACnet/SC?
Yes — for customers where security policy or insurer requirements call for it, we plan and deploy BACnet/SC with proper TLS certificate management. For most buildings, BACnet/IP with network segmentation remains the practical choice.
Can you troubleshoot a BACnet network we already have?
Yes. We do BACnet audits as a service — Wireshark captures, network sniffing on MS/TP trunks, discovery validation, and a written report on what's broken and what to fix.
RELATED SERVICES

Have a project to scope?

Free estimate on any bacnet scope — installation, integration, retrofit, or service. We'll write you a clear scope and an honest price.