Review available data
Telemetry, utility signals, alarms, BMS/HVAC context, selected documentation, and current process realities.
Pilot
The right pilot works on your own data, not on a generic demo.
A pilot should show where the building already reveals operational blind spots, where better interpretation would improve action, and what rollout path makes sense from there.
What should a useful pilot deliver?
priority issues and anomalies
initial recommendations
rollout direction and operating scope
How do we start?
The first phase is always focused on usable evidence rather than on theoretical scope.
Interpret patterns
Look for anomalies, blind spots, repeated incidents, and where better interpretation would improve action.
Define next steps
Summarize findings, early priorities, service actions, and the most sensible rollout path.
What does the pilot usually need?
Historical data
Enough telemetry history to distinguish stable behavior from real deviation.
Mapping and structure
A basic relation between points, devices, zones, tenants, or buildings so the signals can be understood.
Technical context
Schedules, selected documentation, and known priorities help interpret what normal work should look like.
Three rollout paths after the pilot
The documents describe three operating scopes. They are not artificial packages so much as three levels of operational maturity.
Start
Cloud-first, meter-centric, rule-based anomaly detection, core per-tenant and per-problem views, and the fastest path to basic operational visibility.
minimum viable integration
basic issue list and recommendations
shorter retention and lighter AI layer
Standard
The recommended middle ground with denser data, better data-quality monitoring, improved alerting, stronger prioritization, and a more operational panel.
better history and live monitoring
more reliable anomaly filtering
reporting and KPI view closer to market-standard platforms
Pro
The fullest operating system with deeper retention, local infrastructure where needed, richer AI support, and stronger integration into client processes.
dedicated local or hybrid architecture
AI-led handoff and action flows
integration with broader operational processes
Typical implementation rhythm
The exact pace depends on the building, but the working pattern is repeatable.
1 to 14 days for first data
Once integration and access are in place, the first signals usually appear quickly.
2 to 6 weeks to stable operation
Mapping, threshold tuning, and data-quality work turn the pilot into something reliable enough for daily use.
Module rollout after value is visible
From there, BAAP can expand into deeper utility work, BMS/HVAC context, maintenance processes, and portfolio reporting.
If a pilot is the right next step, we can define it quickly.
A short conversation is usually enough to align on data availability, priorities, and the most sensible first scope.