Automotive programs add a layer of process discipline that pure commercial chips do not face. For one MCU and power-management program, the task was to enter TSMC's CyberShuttle for two nodes at once — 40nm automotive and a legacy 180nm BCD companion.
The technical content was manageable. The hard part was the enrollment and qualification timeline, which we walked through with the customer step by step.
Why two nodes in one window
The MCU needed the 40nm automotive platform for performance and long-term supply, while a power-management companion stayed on a mature 180nm BCD node for cost and proven reliability.
Running both through the same CyberShuttle window kept the program's two silicon streams on a shared, predictable calendar instead of two disjoint schedules.
What the enrollment actually required
CyberShuttle enrollment is not a purchase order — it is a coordinated set of design, documentation and qualification submissions against the foundry's window.
The work that protected the timeline:
- Design kit and rule-deck alignment before the submission cut-off
- Documentation package matching the foundry's enrollment template
- Clear ownership of each submission item across the customer and our team
- A backup plan for any item at risk of missing the window
AEC-Q100 prep running in parallel
Qualification is a marathon, not a milestone. We started AEC-Q100 preparation thinking alongside the shuttle enrollment so that wafer return did not become the start of qualification, but the middle of it.
This meant aligning test structures and characterization plans with the grade targets early, rather than discovering gaps after silicon arrived.
The takeaway for automotive teams
For automotive, the foundry window is the easy part. The discipline is in the documentation, qualification and test planning that must run in parallel from day one.
Teams that treat CyberShuttle as a standalone booking usually find the harder work waiting for them after the wafers land.
