Sensing & telemetry connector
LoRaWAN Network
Pulls low-power wide-area sensors into Fibric: door, leak, temperature, and tank-level readings across a whole campus, on one feed.
View details
← Marketplace
Operator by Fibric
Field Dispatch
A managed pattern for proposing a field dispatch with the supporting context attached.
Ask how Field Dispatch 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
Field Dispatch reads the live picture your sensors and alerts already paint, a leak detector tripping in a plant room, a tank level falling faster than it should, a door held open on a floor nobody is assigned to, and works out who should go. The failure it prevents is the ordinary one: the alert goes to a shared inbox, two people drive to the same site, and the person who arrives first is not the one carrying the right part.
It proposes a dispatch — this person, this site, this reason, with the readings attached. In a managed deployment, deduplication, idempotency, and single-flight controls are used to keep a flapping sensor from opening repeated dispatches. It is managed early access: a deployment engineer wires it into your sensor feeds and comms channels, starting in propose-only mode.
Highlights
- Reads the live picture
- Plans routes
- Proposes a reviewed crew dispatch
- Supported paths can record proposals, policy decisions, attempts, and reported outcomes; duplicate controls reduce recognized retry risk
- 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
- field-ops, routing, dispatch, teams
Authentication
Target operator contract: holds no source credentials and uses only deployment-approved sensor and communications bindings. No public operator runtime is implied.
What it reads
- Sensor events across sites, leak, temperature, door, and tank-level readings
- Which alerts are already assigned, to reduce duplicate-dispatch risk
- The history of past dispatches per site, including what fixed it last time
What it can do
- Proposes contacting the selected person by an approved channel with the readings attached
- Proposes a visit order when several sites need attention on one route
- Escalates to the next person on the list when a dispatch goes unacknowledged
How it works
1
Sense
Sensor events across sites, leak, temperature, door, and tank-level readings.
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 contacting the selected person by an approved channel with the readings attached. 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 sensor feed (LoRaWAN Network or MQTT Broker)
- A comms connector (Twilio, Slack, or Microsoft Teams) 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
MQTT Broker
Subscribes to your IoT fleet. Every sensor topic becomes a governed event with a timestamp, a source, and a tenant it belongs to.
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
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
Support & comms connector
Microsoft Teams
Routes approvals and alerts to the channel that owns the call. One confirm in Teams turns a proposed plan into a vetted action.
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 Field Dispatch 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.