Reference · built on requestOperator by FibricFleet, routes & field

Vehicle Fault

Matches telematics fault codes to the vehicle's active route and proposes pull-in, unit swap, or continue with a shop booking.

Request accessPricing ↗

About

Vehicle Fault is an operator job for the moment a fault code appears on a truck that is out working. It reads the code and its severity from the telematics platform, whether a stop lamp or warning lamp is lit, and how many times the fault has recurred. It reads the route that vehicle is on: stops left, miles left, and the nearest yard. From the maintenance system it reads open issues on the unit and whether a shop slot exists.

It then proposes one of three things: bring the truck in now, swap the load to another unit, or finish the route and book the shop for tonight. The fleet manager approves in chat. The chosen action is written to the routing and maintenance systems once, and the fault as read is kept with it.

This is a reference listing. It documents what Fibric would read from Vehicle Fault and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Fault codes in the Samsara vehicle stats feed: J1939 spnId, fmiId, and txId, OBDII dtcShortCode, and milStatus, per vehicle
  • Geotab FaultData keyed to a Diagnostic, with count, severity, amberWarningLamp, redStopLamp, and malfunctionLamp
  • Motive fault codes from v1/fault_codes with the type of code, when it was first observed, occurrences, and severity
  • Fleetio faults and open issues on the vehicle, and the signed webhook messages Fleetio sends with event, timestamp, triggered_by, and payload
  • The vehicle's active route: Samsara route stops with state and scheduledArrivalTime, or a Motive dispatch, and its position
  • Open work orders in the maintenance system: Fleetio work orders, MaintainX work orders by status, or Fiix WorkOrder records

Proposed actions

  • Target capability: propose a pull-in: the route ended at the current stop, the remaining stops moved to another vehicle, and the yard to return to
  • Target capability: propose a unit swap through Fleetio vehicle assignments, with the stops left carried to the replacement unit's route
  • Target capability: propose continuing the route with a shop booking: a Fleetio work order, a MaintainX work order, or a Fiix WorkOrder
  • Target capability: propose an issue on the vehicle in Fleetio, carrying the code, lamp state, and occurrence count
  • Target capability: propose the decision to the fleet manager in Slack or Microsoft Teams, with the code, its severity, and the miles left

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Pull in a Samsara vehicle with the MIL on

    A J1939 fault with milStatus on arrives in the stats feed while stops remain. The operator proposes ending the route at the current stop and moving the remaining stops, for the fleet manager to approve in Slack.

    With Samsara, Slack

  • Book the shop from a Geotab fault

    FaultData with amberWarningLamp active and a low count is matched to a route with few miles left. The operator proposes finishing the route and a Fleetio work order for the evening.

    With Geotab, Fleetio

  • Swap units on a recurring Motive fault

    A code with many occurrences since it was first observed is matched to a full day of stops. The operator proposes a unit swap at the yard and a MaintainX work order on the failing truck.

    With Motive, MaintainX

  • Open a Fiix work order for a fault near the last stop

    A code with redStopLamp on but a route already near its last stop is proposed as continue plus a Fiix WorkOrder at high priority, with the code and count attached.

    With Fiix, Microsoft Teams

Requirements

  • A telematics connector reporting fault codes with severity or lamp state: Samsara, Geotab, or Motive
  • The vehicle's active route or dispatch from the same platform, so a fault is matched to the stops still ahead
  • A maintenance connector for the booking: Fleetio, MaintainX, or Fiix
  • Slack or Microsoft Teams for the fleet manager's approval
Authentication
Fault codes, routes, and work orders are read and proposed through the telematics, routing, and maintenance connectors you bind; the operator carries no credential of its own.

Limits

  • Severity is what the platform reports. Where a code arrives with no severity or lamp state, the operator asks rather than assumes
  • It matches a code to a route; it does not diagnose the fault or say how far the vehicle can safely travel
  • A fault that clears is reported as closed once the platform says so; the operator does not infer a clear from silence
  • It proposes a booking; it never closes a fault, dismisses a Geotab FaultData record, or marks an inspection defect repaired

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Vehicle Fault ↗

Questions and answers

What does the fleet manager approve?
One of three actions for a named vehicle: pull in now, swap to another unit, or finish the route with a shop booking. Each shows the code, the lamp state or severity, how often it has recurred, and the stops and miles left.
What record is left?
The fault as the platform reported it, with time and count, the route state read, the option proposed and the alternatives, who approved and when, and the route change and work order as the systems accepted them.
Does it ever stop a vehicle or clear a fault by itself?
No. It cannot command a vehicle, and it does not clear, dismiss, or close a fault. It proposes; a person decides; the routing and maintenance systems record the outcome.
Ask about Vehicle Fault

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

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