Operator by Fibric
Predictive Maintenance
A managed early-access pattern for reviewing supported telemetry and proposing a maintenance work order before a suspected fault worsens.
View details
← Marketplace
ConnectorSensing & telemetry
OPC UA
Browses the OPC UA address space and subscribes to the nodes your shop floor actually publishes.
Ask how OPC UA fits what you run.
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.
About
The OPC UA connector connects to your server as a certified client, browses the address space to map the nodes that matter, and creates monitored-item subscriptions so value changes arrive as events with the server's source timestamp and status code intact. It keeps its copy of the model in sync as nodes appear or change, and reads current values on demand when an operator asks a question the subscription does not cover.
Security is the part OPC UA got right, and the connector uses it: encrypted sessions, signed messages, and a node allow-list on top, so it can only see what you granted. Under this listing it is read-only; no writes reach the server. It is managed early access: built and maintained by Fibric, and wired with a Fibric deployment engineer through the early-access program.
Highlights
- Browses the address space
- Subscribes to nodes
- Keeps the model in sync
- Managed target is read-only; downstream actions require a separate governed path
- Kind
- Connector
- Category
- Sensing & telemetry
- Publisher
- Fibric
- Availability
- Early access
- Delivery
- Managed by Fibric; nothing to install
- Data direction
- Read-only
- Pricing
- Early access
- Sold by
- Fibric
- Support
- Developed and supported by Fibric
- Tags
- industrial, protocol, scada, hardware
Authentication
X.509 certificate trust between the Fibric client and your OPC UA server endpoint, with an optional server-side user identity on top.
What it reads
- Machine and line state from subscribed nodes, with source timestamps and status codes
- Process values: speeds, pressures, temperatures, counters
- Address-space structure, so operators reason over named equipment rather than raw tags
What it can do
This is a sensing source: it reads, it does not write. Operators act through the write-capable connectors alongside it.
How it works
1
Sense
Machine and line state from subscribed nodes, with source timestamps and status codes.
2
Reason
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.
3
Act
Nothing. This is a sensing source; operators act through the write-capable connectors alongside it.
Pricing
Managed early access
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.
- Deployment engineer
- Wires and verifies the integration with you during onboarding
- Managed validation
- Review maturity, authority, supported records, and deployment boundaries before go-live
- Execution records
- Supported reads, proposals, policy decisions, and reported outcomes kept for review
- Support from the builders
- Developed, run, and supported directly by Fibric
Requirements
- An OPC UA server endpoint reachable from the connector
- Certificate exchange: your server trusts the Fibric client certificate and vice versa
Your deployment engineer verifies each line with you during onboarding.
Support and resources
Supported by the people who built it
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.
Works with
Listings this is designed to pair with. Each listing has its own live or managed early-access state.
Operator by Fibric
Exception Routing
A managed early-access pattern for identifying line exceptions and proposing reroutes, reschedules, or reviewed dispatches.
View details
Operator by Fibric
Peak Demand
A managed early-access pattern for proposing pre-cooling and staged loads against configured comfort and equipment constraints.
View details
Sensing & telemetry connector
Modbus TCP
Talks to the meters, drives, and PLCs that already run your plant, polling registers on a schedule and normalizing the readings.
View details
Control & actuation connector
PLC Command Bridge
A managed reference bridge for vetted controller commands, with stable-key duplicate suppression, local interlocks, and downstream outcome verification.
View details
This connector is developed, published, and supported by Fibric. It integrates with OPC UA 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
Bring OPC UA into your early-access deployment
Early access means a deployment engineer wires this with you, and it runs propose-only until you approve live actions.