OPEN BUILDING AUTOMATION PLATFORM

Connect, program and run every building — from one platform.

Bring Modbus, M-Bus, BACnet and OPC-UA equipment together, program control logic in the browser, give operators live screens, and manage every site from one place.

See how it works ↓
Field devices connect to edge nodes, which join a site hub and report to central FIELD DEVICESEDGE NODESSITE HUBCENTRAL Heat meter Air handler BACnet device Energy meter Edgecontrol · screensalarms Edgecontrol · screensalarms Sitehub Central
Connects to Modbus TCP M-Bus BACnet/IP OPC-UA
01 · Integration engine

Every field bus. One data model.

AdapTier's integration engine polls and subscribes to your equipment and turns every point into a named, typed value with a quality flag — ready for control, screens and history. Configure it in the browser; changes apply live, without a restart.

  • Modbus TCP, M-Bus, BACnet/IP and OPC-UA
  • Device discovery: M-Bus bus scan, BACnet and OPC-UA browse
  • BACnet COV subscriptions, devices behind routers, and a weekly and exception schedule editor
  • Every value carries a quality flag — good or bad, with the reason
  • Writes are checked against each point's limits and state texts before they reach the device
  • Sandboxed scripts decode proprietary formats
configurator · live values
Configurator with a device tree and a live table of polled values
BACnet weekly schedule editor
02 · PLC in the browser

IEC 61131-3. No install.

Write control logic in Function Block Diagram or Structured Text, deploy it to the edge from the browser, and debug it online with live values on the wires.

  • Function Block Diagram and Structured Text
  • Online debugging with live values and forcing
  • RETAIN variables are saved to disk periodically and restored after a restart or redeploy
  • Multiple tasks at independent cycle times
  • 206 standard functions and type conversions
  • Version history with diffs, Codesys import and PLCopen XML export
  • A built-in Modbus TCP server exposes PLC variables to existing systems
PLC editor · online● ONLINE
Function Block Diagram online, with live values on each wire
Structured Text with inline live values
03 · Operator screens

Live process screens. On every site.

Operators get process schematics in any browser — live values on open, setpoints and commands at a click, alarms and history one step away. Each customer's screens live in one central library and are published to every edge.

  • Schematics show live values the moment they open
  • Stale, invalid and manually overridden values are marked
  • Setpoint and command popups enforce each point's limits
  • History charts per point, alarms with acknowledgement, and a site map coloured by alarm state
  • Publish a screen change once — it reaches every edge in about ten seconds and keeps working offline
operator screen · live LIVE
Process schematic with live values
Setpoint popup rejecting a value outside the point's limits
04 · Fleet & updates

Plug in a box. Claim it. Done.

New edge nodes announce themselves; you assign them to a customer and site, and their applications deploy. Updates roll out the same way to every site.

  • Onboarding by claim — a hardware swap is a re-claim into the same slot
  • Staged rollouts: a canary first, then the rest — halting on a failing node, with rollback
  • Updates from the release feed are signed and verified before they can be deployed
  • Downgrades are refused unless explicitly allowed
  • Per-node settings and live logs from the central console
fleet · edges
Fleet console listing edge nodes with status and application versions
Rollouts list with one rollout completed and one running
05 · Distributed BMS

Every building runs on its own. Together, one system.

Each AdapTier node runs its control, screens and alarms locally. Nodes in a building join a site hub, and sites report to central. Lose the internet and every building keeps running.

Two buildings, each with edge nodes and a site hub, connected to central over the internet BUILDING ABUILDING BCENTRAL Centrallatest values · events · alarms Site hub Edgelocal control Edgelocal control Site hub Edgelocal control Edgelocal control internet internet down — every building keeps running
  • Local control, screens and alarms on every node
  • A site hub keeps control and screens running across a site's nodes when the internet is down
  • If the hub fails, nodes fall back to a direct cloud link automatically
  • Central keeps the latest value of every point, and by default 30 days of events and 365 days of alarms
  • Each customer's data is isolated from every other customer's
  • After a week, a site catches central up in 44 seconds — about 200 kB — because only the latest value of each point crosses the internet
UpdatesSigned releasesFeed releases are signed and checked against a pinned key and a checksum before they can be deployed.
RolloutsDowngrade protectionMoving an application backwards is refused unless explicitly allowed.
ControlController watchdogA stalled PLC raises an alarm within a minute.
DataQuality on every valueEvery value is marked good or bad, with the reason when it is bad.

Under the hood: an open messaging backbone (NATS) connects every node — no proprietary middleware.

See it running on your buildings.

Integration, PLC, operator screens, fleet management and distributed operation — one platform, from a single plant room to a portfolio.