Controller Overview
Aida Controller is the on-site appliance for a building. It discovers and controls OT devices on the LAN, hosts the operator UI, runs schedules and modules, and syncs with Aida Platform when cloud connectivity is available.
You use the Platform in a browser for portfolio, licensing, and intelligence. You use the controller for facility structure, commissioning, live control, and offline-capable automation.
Aida Platform (cloud) → Aida Controller (edge) → OT devices (field)
What the controller owns
| Area | Purpose |
|---|---|
| Operations | Dashboard, manual control, schedules, events, automation |
| Monitors | Energy, comfort, maintenance, occupancy, and levels scores (licensed) |
| Commissioning | Groups, discovery, devices, configuration, terminal, firmware |
| Facility | Floors, floor plans, and typed zones |
| Modules | Optional extensions (lighting intelligence, gateways, BMS, integrations) |
| System | Settings, software updates, network, cloud, users, docs, redundancy |
The controller keeps working on the LAN if the WAN link drops. Licenses and facility data stay on the appliance; Platform shows snapshots and remote access when connected.
How it fits with Platform
| On the controller | On the Platform |
|---|---|
| Authoritative floors, zones, groups, devices | Browse Facility snapshot; manage sites & buildings |
| Live control and commissioning | Remote UI tunnel; Assistant / Agents scoped to controllers |
| Apply license blob if air-gapped | Provision install and apply licenses |
| Local users and API keys | Portfolio users and Platform API keys |
Getting set up
- Install — Provision with a one-time Platform install code (or reinstall with a known id)
- Confirm the controller appears on your Platform site and has a license
- Commission devices and define facility structure
- Optionally enable HA redundancy or modules