In short
When a foundry moves a shuttle or lot date, the whole back end of the program moves with it: packaging, test, characterisation, firmware bring-up, the customer's sample commitment. If those are re-planned in the same hour, the slip is contained to the fab's days. If they are re-planned at the next review, each team has spent the gap working to a wrong date. Tymeline reads the foundry traffic and re-plans the dependent work the hour the date changes.
What depends on the shuttle date
Nearly everything after tape-out:
- The assembly and packaging slot, often booked weeks ahead.
- Tester time and the test program's readiness.
- Characterisation and reliability lots, and the oven time behind them.
- The firmware team's bring-up plan and the boards it needs.
- The sample date promised to the customer, and whatever they have planned around it.
Making the response automatic
The foundry's new date arrives in an email. Tymeline reads it, holds it against every commitment that depends on it, and re-plans each one the same hour, with the owners told and the fix in front of the approver where a decision is needed. The customer hears about it from you, that day, with a recovered date rather than a problem.