Existing protocols
The practical starting point is the data the building already exposes through supported protocols, exports, or APIs.
Built above existing systems
BAAP sits above what already runs in the building.
We work with existing telemetry, metering, BMS/HVAC, logs, and documentation through the sources already available in the building. The goal is a readable operating model, not a blank-slate architecture.
Typical inputs
- remote metering and utility data
- BMS/HVAC signals and events
- logs, documents, and asset structure
- CMMS or helpdesk processes where needed
Built to work across vendors
An interpretation layer above existing systems.
- Team & service
Priorities, evidence, next checks
- BAAP
Connect · contextualize · interpret
- Existing systems
Meters · BMS / HVAC · logs · documents
Available connections and control permissions are agreed for each site. Recommendations support the team; automatic control requires an agreed scope.
Gateway and normalization
Signals are terminated, buffered, named, and mapped consistently so the platform can reason about them.
Cloud, hybrid, or local
Deployment mode depends on the building, the data volume, and the security requirements rather than on a one-size-fits-all rule.
No forced replacement
The first value should come from interpretation and operating clarity, not from rebuilding infrastructure that already works.
Data quality is treated as part of the product
Completeness and delays
BAAP tracks whether data arrives, how late it arrives, and where gaps begin to damage confidence.
Outliers and impossible values
Resets, overflows, negative readings, and unstable measurements are handled as explicit quality issues.
Trust in signals
Operators can distinguish between a real building problem and a telemetry problem instead of guessing.
Operational integration matters as much as data integration
In mature organizations, incidents should not end with a notification. BAAP can support handoff into CMMS, helpdesk, reporting, and other operating processes so signals actually become accountable action.
Security, access control, auditability, and deployment mode are also part of the design. The product is meant to be stable inside real organizations, not only inside a demo environment.
The safest way to evaluate the fit is with a focused pilot.
That gives everyone a shared view of the data reality, the signal quality, and the operational opportunities before a wider rollout.