Building automation system (BAS) features vary dramatically in actual value. Some features genuinely improve building operations and produce real savings. Others are marketing-driven additions that don't justify their integration cost.
I've specified, commissioned, and operated BAS across approximately 30 commercial buildings. The patterns are clear about which features earn their cost.
Here are six BAS features that consistently justify their inclusion and four that consistently don't.
The 6 features worth having
1. Centralized scheduling control
The ability to schedule HVAC operation centrally based on actual occupancy rather than running fixed schedules.
Why it earns its cost: Most buildings have substantial schedule-related energy savings opportunities. Centralized scheduling captures them efficiently.
What it requires: Network connectivity, controllable equipment, scheduling capability.
Typical savings: 5-15% of HVAC energy through proper scheduling.
2. Setpoint monitoring and trending
Continuous logging of temperature setpoints, actual values, and equipment status across the building.
Why it earns its cost: Trending data identifies operational problems early. Substantial energy waste from broken or poorly-tuned equipment becomes visible.
What it requires: Substantial data storage and reporting capability.
Typical savings: Indirect through faster identification of operational problems.
3. Alarm and exception monitoring
Notification when equipment operates outside acceptable parameters.
Why it earns its cost: Equipment failures often go undetected until they produce occupant complaints. Earlier identification reduces downtime and prevents extended waste.
What it requires: Alarm setup, notification infrastructure, response procedures.
Typical benefit: Substantial reduction in undetected operational issues.
4. Demand response capability
Ability to reduce electrical load during utility demand events.
Why it earns its cost: Demand response programs typically pay participating buildings substantial amounts for limited curtailment. The economics work for buildings with substantial electrical loads.
What it requires: Utility program participation, communication infrastructure, controllable loads.
Typical revenue: $1-5 per kW of curtailed capacity per event, multiple events annually.
5. Energy use monitoring with submetering
Detailed monitoring of energy use by system, area, or function.
Why it earns its cost: Detailed data identifies specific waste opportunities. The improvements pay back the metering investment quickly.
What it requires: Submetering infrastructure, data collection, analysis capability.
Typical savings: 5-10% of building energy through identified-and-addressed waste.
6. Remote diagnostics and override
Ability to diagnose and address equipment issues remotely.
Why it earns its cost: Reduces emergency service calls. Allows faster response to operational issues.
What it requires: Network access, security infrastructure, technician capability.
Typical benefit: Reduced service costs, faster issue resolution, less downtime.
The 4 features that don't earn their cost
1. Predictive maintenance algorithms in most buildings
AI-driven predictive maintenance promising to identify failures before they occur.
Why it doesn't earn its cost: The algorithms require substantial data and validation. Most commercial buildings don't have the operational scale or data quality to support effective algorithms. Standard preventive maintenance produces most of the available benefit at much lower cost.
Where it works: Very large facilities (100k+ sqft) with substantial mission-critical operations and substantial data infrastructure.
2. Occupant comfort polling and adjustment
Systems that poll occupants for comfort feedback and adjust accordingly.
Why it doesn't earn its cost: Occupant feedback is highly variable and often contradictory. Implementation produces small comfort improvements at substantial integration cost. Most buildings benefit more from setpoint discipline than from feedback-driven adjustments.
Where it might work: Specific high-end office environments with substantial occupant satisfaction emphasis.
3. Comprehensive integration with non-HVAC systems
BAS integration with security, lighting, IT systems claiming substantial cross-system benefits.
Why it often doesn't earn its cost: Integration complexity is substantial. Cross-system benefits are typically modest. Specific point integrations (lighting-HVAC interaction in zones, for example) provide most realizable benefit without comprehensive integration.
Where it works: Very large campuses or specific high-security environments where integration is genuinely valuable.
4. Sophisticated optimization algorithms
Algorithms claiming to optimize building operation through sophisticated mathematical optimization.
Why it often doesn't earn its cost: The optimization gains over good baseline operation are typically modest. The algorithms require substantial commissioning and tuning. Standard control strategies capture most available efficiency.
Where it might work: Very specific applications (data centers, specific industrial processes) where optimization gains are substantial.
What separates the categories
Worthwhile BAS features share characteristics:
Address specific identified building operational needs.
Have clear mechanisms for value creation.
Produce measurable benefits in typical buildings.
Don't require substantial specialized expertise to operate.
Less worthwhile features share different characteristics:
Promise general improvements through complex mechanisms.
Require substantial expertise to set up and maintain.
Produce benefits that depend on specific conditions.
Often duplicate benefits available through simpler approaches.
The distinction matters for BAS specification decisions.
The integration question
BAS integration with broader building systems is often oversold:
Promised "single pane of glass" management often produces complex interfaces that don't deliver promised simplification.
Cross-system integration adds substantial complexity to commissioning, operation, and maintenance.
The integration benefits are usually smaller than initial expectations.
Specific point integrations (lighting controls integrated with HVAC for occupancy, for example) provide substantial benefit. Comprehensive integration rarely justifies the additional cost.
Realistic integration scope produces better outcomes than ambitious comprehensive integration.
The vendor and protocol questions
BAS specification involves substantial vendor and protocol decisions:
BACnet vs proprietary protocols. BACnet is the dominant open protocol. Specifying BACnet supports vendor independence over equipment lifecycle.
Major BAS vendors (Siemens, Honeywell, Johnson Controls, Schneider, etc.). Each has specific strengths and integration ecosystems. Vendor selection should match facility conditions and operating capability.
Cloud-connected vs on-premises. Different security and operational profiles. The choice depends on specific facility requirements.
Open vs closed ecosystems. More open systems support better long-term flexibility. Closed systems may offer better immediate integration.
The decisions affect long-term building operation substantially.
The cost realities
BAS costs vary substantially:
Basic BAS for substantial commercial buildings: $1-3 per square foot.
Comprehensive BAS with extensive features: $5-12 per square foot.
Operations and maintenance: $0.10-0.30 per square foot annually.
Software updates and platform fees: variable but typically substantial.
The cumulative cost across building life is substantial. The cost should match actual value rather than aspirational features.
Specifying BAS for new construction
For new construction BAS specification:
Specify open protocols (BACnet primarily) for vendor independence.
Specify proven features rather than cutting-edge capabilities.
Plan for substantial commissioning. BAS performance depends substantially on commissioning quality.
Document operational assumptions and procedures.
Train operators substantially. BAS that operators can't use effectively doesn't deliver promised benefits.
The specifications matter for building outcomes across decades.
Adding BAS to existing buildings
Retrofit BAS additions face specific challenges:
Existing equipment may not be BAS-compatible without substantial modifications.
Wiring infrastructure may not support BAS sensor and control needs.
Operating procedures need substantial development for BAS-supported operation.
Staff need training in new operational approaches.
The retrofit challenges often exceed initial expectations. Realistic project scoping produces better outcomes.
Operating BAS effectively
BAS effectiveness depends on operational practices:
Trending data should be reviewed regularly. Trends reveal operational issues that point-in-time observations miss.
Alarms should be tuned to provide actionable signals rather than nuisance noise.
Setpoints should be reviewed periodically. Drift from optimal setpoints accumulates over time.
Software updates should be applied carefully. Updates can affect existing functionality.
Documentation should be maintained. Building changes affect BAS configuration that must be documented.
Operational discipline matters more than feature richness.
Common BAS implementation failures
Specific patterns that produce BAS failures:
Poor commissioning. BAS systems that aren't fully commissioned operate suboptimally for years.
Inadequate operator training. Operators who don't understand the BAS produce poor results regardless of system capability.
Documentation drift. Building changes that aren't reflected in BAS produce growing operational issues.
Vendor lock-in. Closed systems make future upgrades or vendor changes substantially harder.
Feature overspecification. Systems with features beyond operational capability produce complexity without proportional benefit.
Each failure pattern is preventable through better practices.
What to ask vendors
For BAS vendor evaluation:
What protocols does the system support?
What's the commissioning approach and documentation?
What does ongoing support cost?
What's the upgrade path for the next 10 years?
How do you train operators?
Can I get references from similar buildings?
What happens if I want to change vendors later?
The questions reveal important factors that affect long-term satisfaction.
The operations contract reality
Many BAS implementations include ongoing service contracts:
The contracts often charge substantial recurring fees.
The services provided vary substantially across vendors.
The contracts can become substantial portions of building operating costs.
Evaluating contract necessity vs. internal capability matters financially.
Some contracts provide substantial value; others don't justify their cost.
Realistic evaluation of operations support requirements supports better financial outcomes.
The honest summary
Six BAS features consistently justify their inclusion. Four don't justify the substantial integration cost they require.
For facility managers and engineers, the framework supports better BAS specification and operation. Buildings get the operational benefits available without paying for features that don't deliver.
For the broader building industry, more accurate BAS evaluation supports better aggregate building decisions.
The BAS market includes substantial marketing-driven feature claims. Evaluation skepticism enables better navigation of this market.
Building automation can deliver substantial value when properly specified, commissioned, and operated. The conditions are achievable but not automatic. Active engagement with the system substantially affects outcomes.
Apply the framework. Specify thoughtfully. Operate effectively. The buildings will operate better as a result.
