How do I choose between different building automation system software platforms for a mixed-use portfolio?

Choosing a building automation system (BAS) software platform for a mixed-use portfolio is mostly about fit across portfolio scale, interoperability, operations, and lifecycle cost rather than just features. The right choice usually comes from comparing platforms against a clear set of requirements.

1) Start with your portfolio goals

Define what you want the BAS to do across the portfolio:

• Reduce energy use and peak demand
• Standardize operations across buildings
• Improve tenant comfort and complaints response
• Centralize alarms, trends, and reporting
• Support fault detection and analytics
• Enable remote operations
• Integrate with meters, lighting, access control, IAQ, EV charging, etc.
• Simplify maintenance and contractor access
• Future-proof for expansions or retrofits

Mixed-use portfolios often need different operational modes for:

• Office
• Retail
• Residential
• Hospitality
• Parking/amenities

So the software should handle diverse schedules, setpoints, and reporting needs.

2) Evaluate core technical criteria

Look closely at these areas:

Interoperability

This is usually the biggest issue.

Check whether the platform supports:

• BACnet/IP, BACnet MS/TP
• Modbus TCP/RTU
• LonWorks if you have legacy systems
• KNX, OPC UA, MQTT, API access
• Open integration with meters, VAVs, chillers, boilers, lighting, elevators, etc.

Questions to ask:

• Can it integrate with multi-vendor equipment?
• Does it require proprietary controllers or front-end software?
• How easy is it to add third-party devices later?

Scalability

Make sure it can grow from a few buildings to the full portfolio.

Check:

• Point count limits
• Number of supported sites
• Multi-site dashboards
• Hierarchical organization by campus/building/floor/system
• Performance with large trend and alarm volumes

Data and analytics

Modern BAS platforms should provide:

• Trending
• Dashboards
• Alarm management
• Energy reporting
• FDD/fault analytics
• Benchmarking across sites
• Export/API access for BI tools

Ask whether analytics are native or require separate software.

Cybersecurity

This is critical, especially for remote access.

Check for:

• Role-based access control
• MFA/SSO support
• Audit logs
• Network segmentation guidance
• Secure remote access/VPN options
• Patch management and vendor security practices
• Alignment with standards like IEC 62443 where possible

Reliability and offline operation

A cloud platform may be fine for portfolio visibility, but local control should still work if internet drops.

Ask:

• Do controllers continue operating locally?
• What happens if the cloud connection fails?
• Are alarms buffered and synchronized later?

3) Consider deployment model

There are three common models:

On-premises

Best if you need:

• Maximum local control
• Tight IT/security restrictions
• Legacy site-by-site deployment

Tradeoffs:

• Higher maintenance burden
• Harder to standardize across many sites
• More internal IT support needed

Cloud-hosted / SaaS

Best if you need:

• Portfolio-wide visibility
• Remote operations
• Faster rollout
• Easier analytics and reporting

Tradeoffs:

• Subscription costs
• Dependence on internet connectivity
• Vendor lock-in risk if data export is limited

Hybrid

Often the best fit for mixed-use portfolios:

• Local controllers at each site
• Cloud layer for central monitoring, analytics, and reporting

This gives you local resilience and centralized oversight.

4) Compare vendor lock-in risk

A platform can look great initially but become expensive later if it is too proprietary.

Evaluate:

• Use of open protocols
• Ability to replace front-end software without replacing controllers
• Data ownership and export rights
• Availability of documentation
• Third-party integration support
• Hardware sourcing flexibility

If the software only works well with a single vendor’s hardware, make sure that strategic dependency is acceptable.

5) Assess operations and user experience

The best BAS is one your operators can actually use.

Look for:

• Clean navigation across multiple building types
• Simple alarm prioritization
• Mobile-friendly access
• Easy trend charting and report generation
• Customizable dashboards by role
• Intuitive scheduling and overrides
• Simple onboarding for operators and contractors

Ask operators to test real tasks:

• Find an alarm source
• Override a schedule
• Compare energy use between two buildings
• Pull a trend report
• Acknowledge and document a fault

6) Check implementation and support quality

Software is only as good as its deployment team.

Ask about:

• Commissioning support
• Training quality
• Integration services
• Local service availability
• SLA response times
• Upgrade process
• Reference projects similar to yours

For mixed-use portfolios, a platform with strong vendor support and a good systems integrator can be more valuable than a feature-rich platform with weak implementation support.

7) Build a scoring matrix

Create a weighted scorecard. Example categories:

• Interoperability: 20%
• Portfolio scalability: 15%
• Cybersecurity: 15%
• Analytics/reporting: 15%
• User experience: 10%
• Deployment model fit: 10%
• Vendor support: 10%
• Total cost of ownership: 10%
• Data export/flexibility: 5%

Score each platform 1–5 and multiply by weights.

8) Compare total cost of ownership, not just license cost

Include:

• Software licensing/subscription
• Controller and gateway costs
• Integration engineering
• Commissioning
• Training
• Ongoing support
• Cloud fees
• Cybersecurity and IT overhead
• Future expansion costs
• Replacement risk if the platform becomes obsolete

Sometimes a platform with a higher upfront cost has lower lifecycle cost because it reduces engineering and operating effort.

9) Pilot before full rollout

For a mixed-use portfolio, a pilot is very helpful.

Choose one site with a representative mix of systems and use cases. Test:

• Integration with existing equipment
• Alarm handling
• Trend performance
• Remote access
• Reporting
• Operator workflow
• Cybersecurity controls
• Data export

Then validate that the pilot can scale to the rest of the portfolio.

10) Practical recommendation

For most mixed-use portfolios, the best choice is usually a platform that is:

• Open-protocol friendly
• Hybrid or cloud-enabled
• Strong on multi-site analytics
• Secure by design
• Easy for operators
• Supported by a competent local integrator
• Not overly dependent on one vendor’s hardware

Quick decision rule

• If your priority is standardization and portfolio visibility, lean toward a cloud-enabled hybrid platform.
• If your priority is legacy integration and local autonomy, lean toward an open on-prem or hybrid platform.
• If your priority is lowest risk of lock-in, prioritize open standards and data export above all else.

If you want, I can also give you:

1. a vendor comparison checklist,
2. a weighted scorecard template, or
3. a recommended architecture for mixed-use portfolios.