Architecture overview
Aida separates cloud portfolio management from on-site control. You use the platform in a browser; each site runs one or more controllers that talk to operational technology (OT) devices on the building network.
High-level architecture
| Layer | Role |
|---|---|
| Platform | Sites, buildings, controllers, users & access, licensing, facility snapshots, telemetry history, Assistant, Agents, integrations |
| Controller | Facility structure, commissioning, live control, schedules, automation, modules — works offline on the LAN |
| OT devices | Lights, shades, HVAC, sensors, access, and other field equipment connected to the controller |
Platform (cloud) → Controller (edge) → OT devices (field)
How the pieces relate for users
Site
├── Building(s) ← logical scope for roll-up and AI (optional)
│ └── Controller(s) ← whole controllers assigned to a building
└── Controller(s) ← also listed at site even if unassigned to a building
└── Facility ← floors, zones, groups, devices (on the controller;
platform shows a synced snapshot)
- Site — Customer location / workspace in the platform.
- Building — Platform grouping of controllers (and thus their spaces) for dashboards and agents. Not a duplicate floor-plan editor.
- Controller — On-site appliance that owns the real facility model and control.
- Facility (platform page) — Read-only (or refreshable) cloud view of that controller’s facility model.
What the platform does vs the controller
| Concern | Where it lives |
|---|---|
| Sign-in, RBAC, multi-site portfolio | Platform |
| Create sites / buildings / assign controllers | Platform |
| Apply Trial / Basic / Pro licenses | Platform → delivered to controller |
| Floors, zones, groups, devices, live setpoints | Controller (authoritative) |
| Browse facility structure from the cloud | Platform Facility (snapshot) |
| Day-to-day control & automation | Controller (local UI or remote tunnel) |
| Energy / comfort / maintenance intelligence | Controller monitors + platform Agents / Assistant |
| Webex, Splunk, Cisco Spaces, etc. | Platform Integrations at site scope |
The platform does not replace the controller as the source of truth for facility structure or live control.
Data the platform keeps
- Snapshots of each controller’s facility model (for Facility, Agents scope, Assistant context)
- Ingested telemetry for history and intelligence
- Site membership, building assignments, users, and licenses
Refreshing Facility pulls the latest model from the controller when connectivity allows.
Security (user view)
- Sign-in with password and optional MFA; enterprise SSO where configured
- Access is scoped by site and role
- Controllers can keep operating on the LAN if the cloud link is down; licenses remain valid through their term