1. Purpose and scope
A package technology is developed for many future products, not for one. The roadmap stage decides which technology to build next and why, by reading what the products of lead customers will need from their packages in the years ahead: more bandwidth between dies, more power delivered through the package, more heat removed, a thinner or smaller outline, a lower cost per connection, or reliability in harsher conditions. The output is a technology with a clear reason to exist, a funded team and lead customers committed to develop it.
The stage is mostly analysis and negotiation. Roadmap analysts and package architects compare the drivers with what existing technologies can do and name the gaps. Cost engineers build a first package cost model. Business development and customer program managers find the customers whose products sit at the edge of those gaps and agree how to develop the technology with them. Quality staff open the quality plan, and trade compliance staff classify the technology and its data before anything is shared.
In scope: customer and market drivers, the technology gap analysis, the roadmap position, the development charter, the technology business case and investment plan, the export control classification and the joint development agreement. Out of scope: choosing the package structure, which belongs to Concept & Test Vehicle Design, and any engineering commitment to targets beyond the direction the drivers set.
13 more sections for registered members.