A test station is blocking valid vehicle-controller units while the line still needs to catch real CAN faults.
Production throughput depends on clearing false failures, while traceable final testing protects the fleet from defective controllers.
Who you’d be doing this for
“My operations lead asked why empty docks are growing again, and I don’t have replacement bikes to point to.”
Fumiko He · Public Mobility Program Manager
Oversees a city bike-share program whose service level depends on replacement e-bikes reaching the fleet.
What is at stake
Valid vehicle-controller units are failing final test and cannot receive release labels. You must restore output without letting a genuine CAN fault pass into the fleet.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- line throughput vs. fault coverage
- fixture evidence vs. supplier containment
- fast retest vs. traceable release
- station logic vs. firmware change
Why Lyft
E-bike availability across station-based networks depends on factory test stations releasing safe vehicle-controller units at production rate.
Written with these in mind
Not your kind of problem? 66 more at Lyft, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.