
Operator by Fibric
Shift Coverage
Keeps a shift staffed to the work in front of it: spots the gap, proposes the cover, and confirms before anyone is moved.
Commons signalFree
The transit and road disruptions your workforce actually rides through, as scheduling signals.
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.
This Commons feed reads GTFS-realtime service alerts and 511 program feeds: transit delays, line suspensions, and major road events for the regions where your people work. A morning line suspension is a shift-start risk for everyone who rides it; this feed makes that legible before the shift starts.
Upstreams are free; regional 511 programs issue free API keys and transit agencies publish GTFS-realtime openly. Paired with a scheduling operator and a comms connector, the play is a risk alert into the channel the shift lead already reads.
A free API key from your regional 511 program where required; many GTFS-realtime feeds are keyless.
This is a sensing source: it reads, it does not write. Operators act through the write-capable connectors alongside it.
GTFS-realtime service alerts: delays, detours, suspensions.
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.
Commons signal feeds are free with every Fibric plan. The upstream data is public; Fibric adds the governance: provenance on every event, deduplication, and receipts when an operator acts on it. You pay for operators, never for signals.
Your deployment engineer verifies each line with you during onboarding.
This signal feed 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
Keeps a shift staffed to the work in front of it: spots the gap, proposes the cover, and confirms before anyone is moved.

Operator by Fibric
Clears the exception before it stalls the line, rerouting work and dispatching the fix the moment flow breaks on the floor.
Control & actuation connector
Calls and texts the right person when an operator decides to act. Messages are throttled and deduplicated, so one event never becomes a flood.
Support & comms connector
Posts the proposed action, waits for the human confirm, then executes, all inside a channel that keeps the record.
This Commons signal feed is developed, published, and supported by Fibric. It reads public data published by GTFS-realtime / 511 programs (api.511.org). Upstream agencies and projects 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.