In building automation, the highest-cost failures are rarely caused by devices. They are caused by missing or inconsistent scope: unclear integration boundaries, incomplete points, inconsistent naming, undocumented network requirements, and site-level ambiguity. Those gaps explode into RFIs, change orders, delayed commissioning, and a messy turnover. Division 25 (Integrated Automation) exists to prevent that outcome. It defines system architecture, integration responsibilities, point naming and tagging, network and cybersecurity expectations, testing and acceptance, and deliverables that make commissioning verifiable. Although many people label it “Mechanical Engineering” because the controlled equipment is often HVAC, Division 25 is fundamentally a controls/automation and OT discipline—closely tied to Electrical and IT. When specified and executed correctly, it delivers quantifiable results: fewer RFIs/COs, fewer deficiencies, and an auditable, maintainable BAS.

Division 25 deliverables that connect the dots between Sequences of Operations, BAS ecosystem, networking constraints, and contractor execution—with defensible assumptions and clean handoffs.

A typical package is structured so each requirement traces cleanly: OPR/SOO → points list → I/O schedule → wiring/termination intent → functional tests → trend validation.

Commissioning fails when requirements are not objectively testable. Our Division 25 deliverables are built for verification: OPR/BoD traceability, SOO → Point List → Functional Test mapping, and unambiguous acceptance criteria—so the CxA can validate intent without interpretation and issues are caught before they become RFIs/COs.

What we enforce in Div 25 (Cx-ready):

• OPR/BoD → SOO → FPT trace matrix (pass/fail thresholds, deadbands, timers, modes)
• Commissioning-grade Point List (units/ranges, writable status, BACnet objects, alarm classes, trend intervals/retention)
• Naming/Tagging standard aligned across drawings, controller DBs, graphics, reports
• Integration matrix (BAS ↔ OT network/VLAN/IP, gateways, protocol mapping, ownership of end-to-end validation)
• Prefunctional + Functional test scripts, FAT/SAT evidence, clean turnover (as-builts, backups, object lists)

Integration risk is rarely “the protocol”—it’s inconsistent object modeling, unclear BIBB/BBMD expectations, undocumented device discovery, and undefined ownership of point mapping and trend/alarm semantics. We apply ASHRAE 135 (BACnet) as an interoperability framework, turning “BACnet-compliant” into verifiable integration requirements—so devices from multiple vendors behave predictably on the same BAS/OT network and commissioning can validate end-to-end data flow.

What we enforce in BACnet integrations (Div 25):

• Network architecture: BACnet/IP vs MS/TP segmentation, router strategy, BBMD/foreign device registration, broadcast domain control
• Interoperability profile: required BIBBs, services, supported object types, COV behavior, time sync, device limits
• Device identity & discovery: device instance governance, addressing/VLAN rules, discovery procedure, documentation of object lists
• Object modeling & semantics: units/ranges, state text, engineering values, alarm classes, priority array handling, command authority
• Point mapping: normalization of names/tags, mapping rules to graphics/reports, consistent metadata for trends/alarms
• Performance & reliability: trend strategy, COV thresholds, polling intervals, network loading limits, watchdogs and comm-fail behavior
• Cyber/IT alignment: OT boundary definition, firewall rule requirements, secure remote access constraints, change control for IP plans

Code compliance is not achieved by drawings alone—it is achieved by how the building operates. Under OBC energy requirements (SB-10), many outcomes depend on controls: schedules, setpoints, deadbands, economizer/ventilation logic, DCV, lockouts, reset strategies, and trend evidence. We translate OBC/SB-10 design intent into verifiable control sequences and measurable operational criteria, so the as-operated building matches the modeled/compliant building—reducing performance gaps, comfort complaints, and post-occupancy fixes.

What we operationalize for OBC/SB-10 alignment (Div 25 / BAS):

• Sequence hardening: occupancy modes, warm-up/cool-down, optimum start/stop, setback/setup logic
• Setpoint governance: heating/cooling setpoints, deadband, sensor tolerances, staged control
• Ventilation control: OA/MA/RA logic, minimum OA enforcement, DCV (CO2), enable/disable criteria
• Economizer & resets: economizer enable/lockout, SAT/DAT reset, static pressure reset, HW/CHW reset strategies
• Equipment lockouts: OAT-based lockouts, interlocks, safeties, freeze protection, alarm response states
• Metering & analytics readiness: energy submeter points, trend intervals/retention, normalization for reporting
• Acceptance & evidence: functional tests + trend proof that sequences and schedules match the compliance assumptions

The gap between design intent and construction execution is not an opinion—it shows up as measurable project friction. Below are widely cited industry metrics and how a Division 25 package targets them directly.

We can start from a sketch, a vendor narrative, or a mechanical SOO. The process is designed to produce actionable deliverables quickly, then iterate with real coordination inputs.

Send your project type, city, and current stage (concept, tender, IFC). We will reply with a practical next step and the minimum information needed to start cleanly.