Reference · built on requestOperator by FibricFleet, routes & field

Charge Readiness

Compares each EV's state of charge and depot charger status with tomorrow's route energy need and proposes a charging order or a swap.

Request accessPricing ↗

About

Charge Readiness runs each evening. It reads state of charge from the vehicle: evStateOfChargeMilliPercent and evChargingStatus from Samsara's stats feed, Soc and DetailedChargeState from Tesla Fleet Telemetry, or Geotab's ChargeEvent with endStateOfCharge. It reads the depot's chargers: port status from ChargePoint's getStationStatus, or StatusNotification and MeterValues from stations speaking OCPP. It reads tomorrow's route for each vehicle from Route4Me or Onfleet and turns distance into energy with the consumption figure you set per model.

Vehicles whose charge will not cover the route are ordered by shortfall. The job proposes which vehicle takes which port first, or a swap to a charged unit. The depot lead approves.

This is a reference listing. It documents what Fibric would read from Charge Readiness 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

  • Samsara vehicle stats evStateOfChargeMilliPercent, evChargingStatus, and evChargingEnergyMicroWh from GET /fleet/vehicles/stats
  • Tesla Fleet Telemetry fields Soc, DetailedChargeState, ChargeAmps, and EstBatteryRange streamed from each VIN
  • Geotab ChargeEvent records with startStateOfCharge, endStateOfCharge, energyConsumedKwh, and chargeType
  • Port status from ChargePoint through getStationStatus: AVAILABLE, INUSE, UNREACHABLE, or UNKNOWN, and load per station from getLoad
  • OCPP StatusNotification with Available, Charging, Faulted, or Unavailable, and MeterValues during a transaction
  • Tomorrow's routes and their vehicle assignment from Route4Me's route.php with vehicle_id, or Onfleet route plans and worker vehicles

Proposed actions

  • Target capability: propose a charging order: RemoteStartTransaction or a Smart Charging profile per OCPP station, sequenced by each vehicle's shortfall
  • Target capability: propose charge_start, set_charge_limit, or set_scheduled_departure for a Tesla vehicle under vehicle_charging_cmds
  • Target capability: propose restoring full load through clearShedState on the ChargePoint group when a shed state would leave a vehicle short
  • Target capability: propose a vehicle swap by changing vehicle_id on the Route4Me route, or the Onfleet task container, to a unit with enough charge
  • Target capability: propose a Slack message to the depot lead through chat.postMessage with the readiness list: vehicle, charge, need, port

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

What you can build

  • Order the depot queue by shortfall

    Read evStateOfChargeMilliPercent for every van, the Route4Me route distance for tomorrow, and OCPP StatusNotification per port, and propose RemoteStartTransaction for the vehicles that need the most first.

    With Samsara, Route4Me, Open Charge Point Protocol (OCPP)

  • Set Tesla departure charging from the route

    For each Tesla, propose set_scheduled_departure and set_charge_limit from the route's start time and energy need, so the car is warm and charged when the driver arrives.

    With Tesla Fleet API, Onfleet

  • Swap in a charged unit

    When a vehicle cannot reach its need by departure on any free port, propose changing the route's vehicle_id to a unit with headroom, and show both in one approval.

    With Route4Me, Geotab

  • Lift a load shed that would strand a route

    If ChargePoint getLoad shows the group shed and a vehicle will fall short, propose clearShedState for the group, with the shortfall shown, for the depot lead's approval.

    With ChargePoint Web Services API

Requirements

  • EVs whose state of charge is readable: Samsara, Tesla Fleet API, or Geotab
  • Depot chargers you can read and command: ChargePoint Web Services, or stations connected to a CSMS that speaks OCPP 1.6 or 2.0.1
  • Tomorrow's route with its distance per vehicle: Route4Me or Onfleet
  • An energy-per-distance figure per vehicle model, set by you, with a reserve margin
Authentication
A Samsara API token with Read Vehicle Statistics, Tesla Fleet API OAuth 2.0 with vehicle_device_data and vehicle_charging_cmds, or a MyGeotab API user; ChargePoint Web Services API License Key and password, or CSMS credentials for OCPP stations; a Route4Me or Onfleet key; a Slack app with chat:write.

Limits

  • Energy need is distance times the figure you set; weather, load, and terrain are not modelled
  • Tesla limits realtime data requests and commands per vehicle per minute and bills per use; the job reads telemetry rather than polling vehicle_data
  • ChargePoint's Web Services API is SOAP only and documents no push; port status is polled
  • A station may answer an OCPP command with NotSupported; the proposal then falls back to a message to the depot lead

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 Charge Readiness ↗

Questions and answers

What does the depot lead approve each evening?
The readiness list: every vehicle with its charge, tomorrow's need, the port and start order proposed, and any swap. One approval covers the order; a swap or a charger command that changes site load is approved on its own line.
What record explains why a vehicle went first?
Per vehicle per night: the state of charge read and its source, the route id and distance, the energy figure used, the shortfall, the port assigned, the command proposed, the decision, and the resulting charge in the morning. Misses are visible next to their inputs.
Will it start or stop charging without approval?
No. Every OCPP, Tesla, or ChargePoint command is a proposal. Once approved, a command is sent once to the named station or VIN. If the vehicle is already charging on a suitable port, no command is proposed.
Ask about Charge Readiness

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