Home / Building Automation

Building automation · Automate module

Your building runs itself, inside the limits you set.

M360 reads schedules, badge-ins, people counts and equipment status, then adjusts setpoints, ventilation and plant operation on its own. Every action is logged and every rule has limits you approve.

M360 · automations · today, live
Example campus · illustrative data

Playbooks

Rules your team can read, approve and pause.

  1. When / then. Each playbook says what triggers it, what it reads, what it is allowed to change and its limits, such as 70–78 °F.
  2. Write it in plain words. Type "pre-cool the boardroom 30 minutes before any meeting over 10 people" and M360 drafts the rule for approval.
  3. Approve, pause, resume. Nothing runs until a facilities admin arms it, and everything it does shows up in the day's log.
M360 · automations · playbooks
Example campus · illustrative data
M360 · automations · occupancy
Example campus · illustrative data

Occupancy

Run the building to how it's really used.

Empty conference room at dusk with an occupancy sensor and thermostat
Booked, empty, set back to standby
  • Booked but empty. A conference room with no one in it ten minutes after the start goes back to standby, 75 °F, until someone walks in.
  • Floors follow badge-ins. Lighting and HVAC come on for the floors people actually go to.
  • Counts, never identities. Room counters, badges and motion give M360 numbers of people, not who they are.

Central plant

The plant runs to the load, not the clock.

M360 watches the chillers, pumps, towers and risers as one system. In the example campus, a 50-ton pony chiller carries the network room overnight so the 2,400-ton central plant can shut down.

  • Night changeover runs from 22:00 to 05:00 as an approved automation.
  • Derated machines are rotated to lag automatically while a finding is open.
Central chiller plant with two water-cooled chillers and insulated piping
M360 · automations · chilled water
Example campus · illustrative data
M360 · automations · when something breaks
Example campus · illustrative data

When something breaks

Fail safe, and tell the right person.

  1. An input fails. If a people counter stops reporting, the rule falls back to badges and motion instead of guessing.
  2. M360 says what it did. Every exception shows what happened, what M360 did and who it told.
  3. Escalation ladder. On-call is paged first, then the next person if nobody acknowledges.

See what your buildings could be telling you.