A clear path when your team needs help.

No. Your building automation system continues to monitor and control the building. Peak Amp uses available data from building systems as part of a broader operational picture.

No. Your CMMS remains the system for managing work orders and maintenance activity. Peak Amp can use maintenance history and help create clearer priorities for the people and systems managing the work.

Not necessarily. Peak Amp starts with the data already available. Additional sensing may be useful where important equipment lacks enough information, but the platform is not built around requiring Peak Amp hardware.

That is a core reason for a vendor-neutral intelligence layer. Available connection methods vary by system, site, permissions, and data quality, so integration is evaluated during discovery.

Peak Amp can begin by assessing what is available and where the gaps are. Incomplete data may limit specific analyses, but it does not automatically prevent a useful pilot.

Peak Amp is positioned as an intelligence and decision-support layer, not the building control system.

Peak Amp is designed to use maintenance and work-order context. The exact connection method depends on the platform and available APIs, exports, or approved data access.

The goal is to show what changed, why it deserves attention, the supporting evidence, and a recommended next step so the facility team can decide and act.

No. Predictive maintenance can be one outcome. The broader goal is to help teams prioritize operational risk, maintenance, repair, and planning decisions across buildings and portfolios.

Yes. A focused building or small group of assets can be a practical way to validate available data, workflows, and value before expanding.