Sensing & telemetry connector
OPC UA
The industrial standard for shop-floor data: browses the address space, subscribes to nodes, and keeps the model in sync.
View details
← Marketplace
Operator by Fibric
Exception Routing
A managed pattern for identifying a line exception early and proposing a reviewed response.
Ask how Exception Routing 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
Exception Routing watches work queues and line state for the small break that becomes a big one: a station reporting a fault while its queue keeps filling, a job stuck in a status nothing transitions out of, a pick wave assigned to a zone that just went down. The cost is rarely the exception itself; it is the fifteen minutes the line runs degraded while someone walks over to find out why.
When flow breaks, the target pattern proposes a reroute, reschedule, or dispatch for review. Any controller write requires a validated connector, local interlocks, stable-key duplicate suppression, and downstream outcome verification. It is managed early access and not a public runtime or install flow.
Highlights
- Reads work queues + line state
- Proposes reroutes, reschedules, and dispatches
- Supported paths can record proposals, policy decisions, attempts, and reported outcomes; duplicate controls reduce recognized retry risk
- Provisioned with a deployment engineer through the early-access program
- Kind
- Operator
- Publisher
- Fibric
- Availability
- Early access
- Delivery
- Managed by Fibric; nothing to install
- Data direction
- Reads and writes
- Pricing
- Included with plan
- Sold by
- Fibric
- Support
- Developed and supported by Fibric
- Tags
- warehouse, throughput, exceptions, dispatch
Authentication
Target operator contract: holds no source credentials and uses only deployment-approved line and communications bindings. No public operator runtime is implied.
What it reads
- Work queues and job status, with how long each item has sat unmoved
- Line and station state over OPC UA or Modbus, including fault codes
- Which stations are healthy right now, so a reroute lands somewhere that works
What it can do
- Proposes rerouting queued work from a faulted station
- Proposes rescheduling a blocked job with the reason attached
- Proposes a reviewed dispatch by text or channel post
How it works
1
Sense
Work queues and job status, with how long each item has sat unmoved.
2
Reason
The target operator contract scores approved inputs and proposes a plan. Live BearScope roles use governed product paths; managed early-access roles require deployment-specific policy, human review, and validation.
3
Act
Target capability: Proposes rerouting queued work from a faulted station. Actual authority, duplicate controls, and recovery depend on the validated deployment and downstream system.
Pricing
Managed scope required
There is no public operator-pack checkout, free trial, or standing rate. Maturity, propose-only evaluation, limits, support, and commercial terms are confirmed during managed review.
- 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
- A line data source (OPC UA or Modbus TCP)
- A command path (PLC Command Bridge) if you want it to act on the line
- A comms connector (Slack or Twilio) for dispatch
Your deployment engineer verifies each line with you during onboarding.
Support and resources
Supported by the people who built it
This operator 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.
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
Support & comms connector
Slack
Posts the proposed action, waits for the human confirm, then executes, all inside a channel that keeps the record.
View details
Control & actuation connector
Twilio
A managed reference connector for calls and texts. Throttling, stable keys, human authority, and delivery reconciliation reduce repeat-send and flood risk.
View details
This operator is developed, published, and supported by Fibric. 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 Exception Routing 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.