
Operator by Fibric
Peak Demand
A managed early-access pattern for proposing pre-cooling and staged loads against configured comfort and equipment constraints.
ConnectorSensing & telemetry
Polls holding registers and coils on the meters, drives, and PLCs that already run your plant.
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.
The Modbus TCP connector polls the devices industrial sites have relied on for decades: power meters, variable-frequency drives, PLCs, and sensor gateways. It reads holding and input registers and coil states on a schedule you set per device, applies your register map to turn raw words into named, scaled values, and emits each reading as a governed event with device, register, and timestamp.
Modbus TCP carries no authentication in the protocol, so the connector runs read-only under this listing and reaches only the unit IDs and register ranges on its allow-list, with access scoped at the network layer. It is managed early access: built and maintained by Fibric, and wired with a Fibric deployment engineer through the early-access program.
Modbus TCP is unauthenticated by design, so access is scoped at the network layer and constrained by the connector's per-device register allow-list.
This is a sensing source: it reads, it does not write. Operators act through the write-capable connectors alongside it.
Power meter readings: kW, kWh, voltage, current, power factor.
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 listing is informational and not self-serve. A deployment review must validate the connector, credentials, action boundary, recovery path, support, and contractual pricing before use.
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.
Listings this is designed to pair with. Each listing has its own live or managed early-access state.

Operator by Fibric
A managed early-access pattern for proposing pre-cooling and staged loads against configured comfort and equipment constraints.

Operator by Fibric
A managed early-access pattern for reviewing supported telemetry and proposing a maintenance work order before a suspected fault worsens.

Operator by Fibric
A managed early-access pattern for identifying line exceptions and proposing reroutes, reschedules, or reviewed dispatches.
Control & actuation connector
A managed reference bridge for vetted controller commands, with stable-key duplicate suppression, local interlocks, and downstream outcome verification.
Sensing & telemetry connector
The industrial standard for shop-floor data: browses the address space, subscribes to nodes, and keeps the model in sync.
This connector is developed, published, and supported by Fibric. It integrates with Modbus TCP 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.