Automation Hub is the building automation rule engine of BuildOT One, the MachineSens IoT cloud platform. It lets teams define When-Then rules that turn alerts, thresholds and schedules into actions, with approvals, permissions and a full audit trail for every execution.
| Key fact | Detail |
|---|---|
| Module | Automation Hub (also called Automation Center) |
| Part of | BuildOT One |
| What it does | Runs event-driven and time-based rules that trigger actions across devices, assets and workflows |
| Data sources | IoT telemetry, device and asset registry, AirBMS system data, predictive and fault detection outputs |
| Integrations | Device control endpoints (uplink and downlink), backend APIs, scheduler and trigger engine |
| Typical users | Facilities managers, building operators, energy managers, system administrators |
| Protocols | BACnet, Modbus, MQTT and LoRaWAN devices connected through BuildOT One |
What Automation Hub does
- Turns conditions into actions. A rule watches for a fault, alert or threshold breach and then runs the action you defined.
- Runs schedules. Time-based rules handle recurring tasks, such as switching settings at set hours.
- Controls how rules go live. Drafts can be reviewed and approved before they are activated, so no one changes building behaviour by accident.
- Records everything. Every execution is logged with its trigger, action, timestamp and outcome.
- Keeps people in control. Permissions decide who can create, edit, approve and run rules.
Building automation rule features
- When-Then rule engine with condition-based triggers
- Rule lifecycle management: create, edit, activate, deactivate and version
- Draft and approval workflow
- Event-driven automation based on faults, alerts and thresholds
- Time-based scheduling for recurring patterns
- Context-aware rules that use asset data and system state
- Execution logs and audit trail with traceability from rule to result
- Validation that blocks invalid or unsafe actions
- Dashboard of active rules, drafts and recent executions
- Rule builder that defines conditions, actions and logic flows using real data sources
- Scheduler interface for recurring execution patterns
- Rule governance that separates system templates, assignments and runtime rules
- Reverse linkage between rules, executions and the resulting system behaviour
- Transparent, traceable logic with no hidden steps
How Automation Hub works
- Build a rule. Choose the condition, the trigger and the action using real data sources.
- Review and approve. The rule stays a draft until it is validated and approved.
- Activate. The rule runs on events such as faults and alerts, or on a schedule.
- Check the log. Each run records its trigger, action, timestamp and outcome.
Who uses it
Operations teams use Automation Hub to cut repetitive manual work and respond faster to faults. Portfolio managers use it to apply the same rules across many buildings, so behaviour is consistent from site to site.
Works with
- AirBMS provides the HVAC and system data that rules act on
- Predictive Center feeds fault and anomaly outputs into rules
- FM360 receives work orders raised by rules
- BuildOT Copilot can link recommendations to automation
- Climate control products such as ThermoSense thermostats are common rule targets
- IO Connect Mini wireless I/O controller for relay and analog output control
- Solution page: Building performance management
Frequently asked questions
What is the difference between Automation Hub and Automation Center?
They are the same module. Automation Hub is the platform name used on this site.
Can a rule change equipment settings automatically?
Rules can trigger actions against connected devices and workflows. Permissions and the approval workflow control who can create and activate them.
How do I know what a rule did?
The execution log records what triggered the rule, what ran and what the outcome was, so every action can be traced.
Can rules be time-based as well as event-based?
Yes. You can use event triggers, schedules or both.
Explore all BuildOT One modules
Want to see rules running on your own building data? Request a demo
