Building Automation Integration
What actually has to talk to what, and who owns the seam. What Division 25 coordinates →
Services
Division 25 & Building Automation
Overview
Integrated automation: how mechanical, electrical, controls and networks are supposed to meet. Architecture, points, sequences, interfaces and documentation — the seams, not a brochure of “smart building” language.
The useful output is a package someone can build and commission against: who owns the point, who owns the sequence, and which test crosses the terminal.
Index
Controls Architecture
Controllers, networks and supervisory layers as one system, not a pile of vendor drawings. BAS network architecture →
System Interfaces
Where Division 23, 26 and 27 actually meet Division 25. Division 25 vs Division 23 →
Sequences of Operation
From written sequence to something a controller can execute without inventing the missing logic. From sequence to architecture →
Points & Integration Requirements
Points lists that survive commissioning because ownership was decided before the panel was landed. Coordinating points and sequences →
Network / OT Coordination
Building networks that share a closet with IT and still have to run. BAS, OT and network →
Division 25 Documentation
Construction-ready integration maps: signal, owner, test.
What we investigate
- Missing or unreliable points
- Sequence mismatch
- Integration failures
- Controller communication problems
- Unclear responsibility boundaries
- BAS / network interface issues
- Alarms or commands not behaving as expected
- Third-party system integration problems
Typical systems
- BAS and field controllers
- Controls networks, including BACnet/IP where installed
- Supervisory workstations
- Metering and lighting control
- Third-party interfaces
Have a problem in this area? Start with the symptoms, the system, and what has already been tried.
