Division 25 Integrated Automation
Performance Specification Gap in Division 25 Integrated Automation submittals
Short answer
A measurable performance property in the submittal (rating, capacity, tolerance, efficiency) does not meet what the spec requires. Default grade in Division 25 Integrated Automation: Blocker.
A measurable performance property in the submittal (rating, capacity, tolerance, efficiency) does not meet what the spec requires. This guide covers how it shows up specifically in Division 25 Integrated Automation submittals.
What to look for in Division 25 Integrated Automation
Key performance parameters in integrated automation submittals:
- Point count capacity (digital inputs, digital outputs, analog inputs, analog outputs) - controller must support the specified number of points without expansion
- Controller memory and processing - RAM, flash storage, and CPU speed must meet or exceed spec for the programmed sequences
- Communication protocol (BACnet/IP, BACnet MS/TP, LonWorks, Modbus RTU/TCP, MQTT) - must match spec exactly
- Network architecture - peer-to-peer vs. hierarchical topology as specified
- Trending and data logging capacity - number of trended points multiplied by sample interval; storage duration
- Graphics workstation count and display resolution - screen count, minimum resolution, concurrent user sessions
- Alarm management - number of priority levels, acknowledgment workflow, response time thresholds
- System integration points - interfaces to HVAC, lighting, fire alarm, access control, metering subsystems
- Energy dashboard reporting interval - real-time vs. 1-minute vs. 15-minute aggregation as specified
- Latency and response time - maximum acceptable delay from sensor input to control output action
- Scalability - ability to add future points or controllers without replacing head-end hardware
- Redundancy and failover - standby server, controller auto-recovery, and battery backup as specified
How severe is it?
Default grade: Blocker. Always a Blocker when the gap touches life-safety or structural performance.
Deviation Check assigns a default per category and escalates or de-escalates based on the spec, always showing its reasoning. See the Division 25 severity rules.
What the PM should do
Treat this as a hold. Do not approve the submittal until the sub resolves it, either by providing the specified product and documentation or by routing an approved substitution or or-equal request. Return the relevant spec passage to the sub as a redline.
Other deviation categories in Division 25
Frequently asked questions
Which controller performance parameters should a PM check first when reviewing a Division 25 Integrated Automation submittal for spec compliance?
Start with point count capacity - digital inputs, digital outputs, analog inputs, and analog outputs - to confirm the controller handles the specified number of points without expansion. Then verify the communication protocol matches exactly: BACnet/IP, BACnet MS/TP, LonWorks, Modbus RTU/TCP, or MQTT as written in the spec. A protocol mismatch is always a blocker.
How do trending capacity and response time requirements create performance gaps in Division 25 Integrated Automation submittals?
The spec sets a specific sample interval and storage duration for trended points; a controller with lower memory or shorter retention fails on those counts. Response time is the maximum delay from sensor input to control output - if the submittal's architecture adds latency beyond the spec threshold, that is a blocker. Redundancy and failover specifications (standby server, controller auto-recovery, battery backup) are checked here as well.
View this page as Markdown for LLMs and note-taking.