
Operator by Fibric
Guest Comfort
Tunes light, air, and access to the rhythm of arrival and rest, balancing comfort against energy spend room by room.
ConnectorSensing & telemetry
Reads objects and properties off the building automation network directly, no gateway box in the rack.
The BACnet/IP connector speaks the protocol your controllers already speak. It discovers devices on the subnet, reads analog and binary objects and their properties (present value, setpoint, status flags), and uses COV subscriptions where controllers support them so a changed value arrives as an event instead of a poll. Setpoints, occupancy, damper positions, and equipment state land in Fibric stamped with device, object, and the moment they changed.
BACnet/IP carries no authentication of its own, so the connector is deliberately read-only in this listing and every readable object sits on an explicit allow-list; access is further scoped by network segment and BBMD configuration. This connector is available now: built and maintained by Fibric, and wired into your site with a Fibric deployment engineer through the early-access program.
BACnet/IP itself has no authentication, so access is scoped by network segment and BBMD configuration plus Fibric's per-object read allow-list.
This is a sensing source: it reads, it does not write. Operators act through the write-capable connectors alongside it.
Zone temperatures, setpoints, and occupancy state per controller.
Operators reason over this connector's signals next to the rest of your stack, so decisions are grounded in the same records you run on.
Nothing. This is a sensing source; operators act through the write-capable connectors alongside it.
This connector is provisioned through the early-access program. A deployment engineer wires it with you as part of onboarding; there is no separate line item and no charge until it carries production traffic.
Answers are based on this listing. For anything it can't answer, our team can.
For anything this page can't answer, talk to us.
Your deployment engineer verifies each line with you during onboarding.
This connector is developed, run, and supported by the same Fibric team. Support starts during onboarding with a named deployment engineer and doesn't hand you off afterward.
The connectors and operators this pairs with in production.

Operator by Fibric
Tunes light, air, and access to the rhythm of arrival and rest, balancing comfort against energy spend room by room.

Operator by Fibric
Shaves peak demand without anyone noticing: pre-cools, stages loads, and respects every comfort and safety guardrail you set.

Operator by Fibric
Hears the equipment going wrong before it fails. It reads vibration and runtime, predicts the fault, and opens the work order early.
Control & actuation connector
Writes setpoints and overrides back to the building management system, fail-closed. Every command leaves a receipt you can audit.
Building platforms connector
Reads and supervises the Metasys building management system: sense the equipment, reason about comfort, act fail-closed.
This connector is developed, published, and supported by Fibric. It integrates with BACnet / IP through published APIs. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy
Early access means a deployment engineer wires this with you, and it runs propose-only until you approve live actions.