OTA Pushes Nine Features: Warehouses Prioritize Fallbacks

Chery Fulwin T11's second full-domain OTA this time added 9 new features and 4 optimizations. Two points caught my eye: remote one-click vehicle preparation and autonomous ETC passage on highways. Behind the car system experience, it looks more like handing over a process to the system to run itself. User presses phone, car prepares in advance; car reaches gate, system identifies, lifts barrier, passes through. This flow is very similar to AGV scheduling I did in warehouses.

When we built warehouse robots, the trouble centered on liability boundaries when things went wrong. Anyone who has run operations in a real warehouse knows: whether shelf positions are occupied, whether to proceed when LiDAR loses points, whether to retreat if the robotic arm grabs crookedly, whether to halt if order system data is dirty—these all need boundaries. Vehicle-side OTA is the same. The more new features, the more it tests exception rollback and permission management. Remote vehicle prep involves AC, seats, power; autonomous ETC passage involves payment, roadside equipment, highway status—multiple systems must coordinate here.

With these 9 new features in the T11, I'm more interested in how it pushes cars from spec-sheet stuffing to process automation. Paper parameters like 27 sensing units and 200 TOPS compute power are certainly important, but daily drivers care more about whether the system dares to keep running in edge cases like no network, no calibration, gate recognition failure, or sudden lane changes by the car ahead. Have you calculated deployment costs? That sentence holds true in the auto industry too.

Car manufacturers shouldn't just release feature lists when pushing OTAs; they should clearly state failure rates, rollback times, manual takeover rates, and safety boundaries. Users don't need weekly reminders that there are a few more features; users need to know upgrades won't break old functions. Same logic in warehouses: we implemented WorkBuddy for master process tables, but key SKUs still require manual verification—we can't hand inventory risk over to full automation. Payment and passage in cars follow the same principle.