For facilities and building services

Your situation

Every look at a controller means a visit, or a fight with IT

Access without the building's IT: The controller is behind someone else's network. Getting in means a site visit, or asking the building's IT for a VPN they do not want to give you.
Controllers waiting for a download: A controller can sit for weeks waiting for a download, or reporting non-operational, and nobody knows until the tenants complain.
Ping is not status: A controller that answers ping may not be doing its job. Nothing tells you until someone goes and looks.
Many buildings, many tools: Each building has its own way in, its own login, and its own person who knows it.

What changes

Each controller asked its status, read-only, every minute

A Relayant box plugs into the building's network and connects out over an encrypted tunnel. It asks each controller its system status over BACnet/IP, with Who-Is and ReadProperty only, and does not write.

Operational, download required, download in progress and non-operational are read as the controller reports them.
Waiting for a download is a warning. Non-operational is a fault that raises an alert.
The controller's own ports you choose get a Relayant address, reachable only from the addresses you list.
Nothing is opened or forwarded on the building's router.

What stays the same

The building's network. The relay reaches only the controller ports you chose, not the building's whole network.

The controller. Checks are read-only. We hold no login for it, and BACnet needs none.

Who gets in. Only the internet addresses you list can reach a controller's Relayant address.

Every minute the box checks each device its own way, such as building controllers over BACnet, read-only. A device that stops answering raises an alert.

The features that matter most

What a facilities contractor uses

BACnet checks

Who-Is and ReadProperty only: the controller's system status, vendor and model. Needs a recent box update at the site; the portal says so.

Alerts

Email, Slack, Microsoft Teams and webhooks, with an Acknowledge link. A warning keeps the controller online; non-operational raises an alert.

Remote access

One address and port per controller port you choose, reachable only from your listed addresses. The relay reaches nothing else on the building's network.

It fits the buildings you already look after

A box, or the agent, on the building's network: A box on a LAN port, or the software agent on a Linux PC already in the plant room. Either dials out; nothing is opened on the router.
The building's IT: The box needs only outbound internet. It asks for no VPN, no open port and no login.
Your technicians: Owners, operators and viewers, two-factor sign-in, and an audit log of who changed what and when.
Many buildings: Every building is a site in one portal, with each controller's state, response time and seven days of availability.

A day with Relayant

What a facilities contractor's day looks like

An example, not a customer's story.

Morning
A controller in one building reports download required. It stays online with a warning in the portal, and you schedule the download for the next visit.
Mid-morning
Another controller reports non-operational. The alert reaches your team by email with the reason in the controller's words.
Afternoon
You connect to that controller through its Relayant address from the office, using your own tool, and find the fault without a visit.
The first of the month
The building's report lists every incident and how quickly your team acknowledged it, ready for the building manager.

Which plan

Relay + Alerts, per box at a live site

BACnet checks are in every plan; the alerts, webhooks, acknowledge links and monthly reports are in Relay + Alerts. See the plans.

Tell us how many buildings you look after, what controllers are in them and how each building connects.

Email [email protected] Sign in

Building controllers watched over BACnet, without the building's IT.