Run the export demo with a fixed acceptance checklist. Ask each vendor to document, in writing, which vehicles and model years are covered, whether the export includes battery management and charging-session fields at the per-VIN event level, how the data is accessed (CSV download or API), and what permissions or add-ons are required. Reject summaries that aggregate by day or fleet; the audit needs event-level records tied to individual vehicles so your analyst can reproduce the degradation estimate outside the vendor interface.
The conditional winner is explicit: choose Samsara for a mixed fleet, and choose Ford Pro for an all-Ford fleet. Neither wins if per-VIN charge-event export fails. A mixed fleet that selects Ford Pro without verified cross-make coverage, or an all-Ford fleet that selects Samsara without verified OEM-depth access, is buying a reporting layer that may not support the retirement decision it is meant to justify.
Treat commercials as a compliance check, not a tiebreaker. Require a line-item quote that separates hardware, software, integration, and data-access terms, and confirm that the export capability shown in the demo is included in the quoted scope. If the lower quote depends on an unwritten export path or a future integration, it is not the compliant quote. The platform that passes the same export test at the lower verified, line-item cost is the operational choice for that fleet.
Costs before any 70% retirement gate
This section alone applies the f7i cost envelope to a 10-van quote gate. Before a fleet uses any platform output to justify a 70% battery-retirement decision in 2026, it should price the monitoring work as a separate line item. According to f7i.ai’s 2026 condition monitoring pricing guide, setup costs range from $500 to $5,000 per asset, plus $100 to $1,000 annually. Treat those figures as a monitoring budget envelope for planning and procurement, not as a Ford Pro or Samsara quote and not as proof that a vendor can deliver the data your retirement gate requires.
| 10-van cost check | Per asset (f7i.ai, 2026) | 10-van total |
|---|---|---|
| Setup | $500–$5,000 | $5,000–$50,000 |
| Annual | $100–$1,000 | $1,000–$10,000 |
The arithmetic is straightforward: 10 vans at $500 to $5,000 each produces a $5,000 to $50,000 setup range, and 10 vans at $100 to $1,000 each produces a $1,000 to $10,000 annual range. Use the same unit before comparing vendors. A per-vehicle-per-month telematics headline is not comparable to a per-asset setup fee until both are annualized over the same period and scoped to the same work. If a quote bundles connectivity, dashboards, and monitoring into one number, ask the vendor to separate one-time setup, recurring software, and any degradation-analysis labor.
Apply a hard quote gate before signing. If a Ford Pro or Samsara quote exceeds $5,000 per asset for setup or $1,000 per asset per year for the monitoring scope tied to the retirement decision, require a written degradation-monitoring scope and a 30-day paid evaluation. The scope should state exactly which charge-event fields will be delivered, how often they are exported, and who is responsible for validating the export against the fleet’s audit requirements.
This cost check does not select a platform; it prevents a dashboard subscription from being mistaken for decision-grade battery evidence. A quote that fits the f7i.ai envelope still must pass the fleet’s data-export audit, while a quote above the envelope should only proceed when the added cost buys documented, testable monitoring capability.
Where the 70% rule breaks
A 70% state-of-health retirement gate can fail even when the underlying data pipeline is sound, because the gate depends on how the contract defines health, how the vehicle is charged, and how operating conditions shape each charge event. Before acting on any threshold, treat the gate as a testable claim: confirm that the measurement method, duty cycle, and environment match the decision you are about to make.
Before day 30, calculate the cost of a wrong retirement call in both directions. For retiring one van early, add the avoided replacement-pack quote to the downtime days multiplied by your daily route cost. For keeping one failed van in service, add towing, missed-route cost, and any emergency pack or service expense. Record both totals in the same worksheet so the 70% gate is weighed against operational consequences, not dashboard confidence alone. As a budgeting reference, F7i.ai reports that condition monitoring setup can range from $500 to $5,000 per asset, plus $100 to $1,000 annually; use your actual vendor quotes and route economics for the retirement math.
Close the pilot with a binary decision. If the export passes the day-30 completeness check and the flagged vans can be reconciled to your contract state-of-health method, the platform is eligible for your retirement workflow. If required fields are missing, event coverage falls short, or false alerts exceed your threshold, pause the 70% gate and correct the data pipeline before removing any van from service. Use the monitoring cost envelope as priced above when weighing the cost of a wrong retirement call, and your actual vendor quotes for the retirement math.
Five if/then rules for the 70% gate
In 2026, a fleet should treat the 70% battery-retirement gate as a data-qualification decision, not a dashboard purchase. Run a 30-day, 12-vehicle charge-event audit before any retirement action, and apply the four if/then rules below to determine whether a platform can support that gate.
Each rule is falsifiable: the vendor either produces the required export and degradation evidence during the audit window, or the platform is excluded from the retirement workflow.Rule 1: If every vehicle in scope is a Ford and Ford Pro exports per-VIN charge-event voltage, current, and temperature for five test VINs, pilot Ford Pro first for the 70% gate. The export must be traceable to each VIN and each charging event so the audit team can confirm that the data package is complete before any retirement recommendation is generated.
Rule 2: If the fleet operates two or more makes and Samsara exports the same per-VIN charge-event voltage, current, and temperature fields, pilot Samsara first. If Samsara cannot produce those fields in a usable export for the audit vehicles, do not use it as the 70% gate. A mixed fleet should not accept a partial integration as a substitute for vehicle-level charge-event evidence.
Rule 3: If either vendor cannot show charge-signal incremental-capacity or equivalent degradation features derived from charging data without requiring low-current discharge, buy the product only as telematics, not as a battery-retirement system. Research indexed as arXiv:2609.22843 describes predicting discharge incremental-capacity features directly from charging signals; a vendor claiming retirement-grade insight should demonstrate an equivalent operational capability on your audit data.
Rule 4: If the 30-day, 12-vehicle audit returns missing timestamps, missing VIN mapping, or gaps in voltage, current, or temperature for any test vehicle, pause the 70% decision. Require a corrected export, rerun the affected checks, and document the failure before the platform is allowed to influence retirement timing.
What to do next
| Step | Action | Why it matters |
|---|---|---|
| 1 | Define your fleet composition and confirm whether every vehicle in scope is a Ford model or a mixed make; document the full VIN list before starting the 30-day, 12-vehicle charge-event audit. | The canonical decision rule routes all-Ford fleets to Ford Pro and mixed fleets to Samsara only if the export test passes, so fleet composition determines which platform to evaluate first. |
| 2 | In Ford Pro (for an all-Ford fleet) or Samsara (for a mixed fleet), run the export test on every VIN in the audit sample and verify that each export includes per-charge voltage, current, temperature, and SoH trend data. | The 70% battery-retirement gate by Q4 2026 requires per-vehicle charge-event data sufficient to estimate incremental-capacity degradation; missing fields invalidate the platform as a battery monitor. |
| 3 | Compare the exported charge-event records against the audit requirements and flag any VIN or charge event where voltage, current, temperature, or SoH trend data is absent or incomplete. | A falsifiable pass/fail check prevents dashboard claims from substituting for the data needed to make a defensible 70% retirement decision. |
| 4 | If the selected platform fails the export test for any VIN in the sample, reject it as a battery monitor for the 70% gate and do not proceed with a retirement decision based on its data. | The decision rule requires rejecting both Ford Pro and Samsara when they cannot produce the required per-charge data for every VIN, regardless of fleet type. |
| 5 | Grounding the Q4 2026 retirement gate in verified, per-vehicle data reduces the risk of premature or delayed battery retirement decisions. | |
| 6 | Before finalizing your platform choice, confirm with the official Ford Pro or Samsara support channels that the required export fields will remain available for your fleet configuration through Q4 2026. | Verifying ongoing data availability ensures the audit results remain valid for the 70% retirement gate and avoids relying on features that may change. |
Frequently Asked Questions
What vehicle-level details must vendors document in writing before the export demo?
Vendors must document in writing which vehicles and model years are covered, how the data is accessed (CSV download or API), and what permissions or add-ons are required.
Which data fields are required in the export to support a battery degradation audit?
The export must include battery management and charging-session fields at the per-VIN event level.
Why are daily or fleet-aggregated summaries insufficient for the audit?
Summaries that aggregate by day or fleet must be rejected because the audit needs event-level records tied to individual vehicles so an analyst can reproduce the degradation estimate outside the vendor interface.
When should a fleet choose Samsara over Ford Pro for battery monitoring?
Samsara should be chosen for a mixed fleet and Ford Pro for an all-Ford fleet, but neither wins if per-VIN charge-event export fails.
What risk does a mixed fleet face if it selects Ford Pro without verified cross-make coverage?
A mixed fleet that selects Ford Pro without verified cross-make coverage is buying a reporting layer that may not support the retirement decision it is meant to justify.
Under what pricing condition should a lower quote be rejected as non-compliant?
A lower quote is not compliant if it depends on an unwritten export path or a future integration, and the compliant choice is the platform that passes the same export test at the lower verified, line-item cost.
Quick answers
| Which platform is recommended for a mixed fleet versus an all-Ford fleet? | Samsara is the conditional choice for a mixed fleet, while Ford Pro is the conditional choice for an all-Ford fleet. |
| Under what condition does neither platform win the selection? | Neither platform wins if per-VIN charge-event export fails. |
| What level of data detail is required for the battery degradation audit? | The audit requires event-level records tied to individual vehicles, and summaries that aggregate by day or fleet should be rejected. |
| What should a vendor's line-item quote include when evaluating export capabilities? | The quote should separate hardware, software, integration, and data-access terms, and confirm that the export capability shown in the demo is included in the quoted scope. |
| When is a lower-priced quote considered non-compliant? | A lower quote is not compliant if it depends on an unwritten export path or a future integration. |
Also worth reading: Roadside Assistance for Fleets 2026: $175/Hour Downtime Threshold — Include or Skip?: Roadside Assistance for Fleets 2026: · Cheap Work Trucks for Fleets: 31 Cents vs 38 Cents Per Mile: Cheap Work Trucks for Fleets: · Shop Floor Scheduling 2026: Artificial Intelligence Cuts Turnaround 15%—Adopt or Wait?: Shop Floor Scheduling 2026: Artificial