by Sheethong Ho,
It is a natural tendency to think that Yield Management Integration is simply a data integration job that gathers related manufacturing and test data into a Yield Management System (such as dataPOWER, PDF), and thereafter the engineers and their Yield Management System live happy ever after.
For the fact that a production environment is never static and is evolving constantly makes the maintenance aspects of the Yield Management System a formidable challenge. It is fairly common to see a facility struggling to have its newly implemented Yield Management System keep up with new production needs. Any intentional or unintentional change in manufacturing data may break the loading of a data feed causing its yield analysis capabilities render useless.
The following are some of the key considerations when designing or selecting a solution for the implementation of a Yield Management System.
- How flexible is the solution in adapting to changing needs in the manufacturing environment? For instance, a new foundry plant is providing the assembly testing that feeds an existing data source for the Yield Management System. However, its test data does not comply with the expected format and could not be processed and loaded. What will be the cost and effort associated with fixing the assembly test data feed?
- How easy is it to manage and administrate the system? Anyone tasked to manage and maintain the data processing and data feed for the Yield Management System will experience a substantial amount of time investigating why a certain data failed to load. Hence, the question: does the solution provide good error reporting and handling? When the system administrator is approached by the yield engineer on a certain high priority lot not appearing in the Yield Management System – what tools are available to help diagnose the problem or to track down the missing lot? Will the system provide any further means to answer these questions:
- Did the test data for the lot make it to the Yield Management system? Perhaps the lot has not even been tested or data was not made available to the system.
- What is the cause for the failure? A typical failure is the missing Meta (e.g. Wafer Map Configuration) data that is required for the loading. (Usually the Process Engineers are responsible in keeping the Meta data updated)
- How the error could be eradicated and the data loading be resumed. What tools are provided to facilitate such activities?
- Does the system provide critical alarms and warnings ahead of time such that problems are not identified only when data are discovered to be missing or incorrect during yield analysis? These alarms and warning could also include system resources such as storage space and CPU usage that could affect the processing and loading of yield related data.
In considering a solution for Yield Management System integration, perhaps more than simply concerning about getting the data accurately into the system, the ease of system maintenance is equally important.
Contact Cimetrix Global Services to discover Cimetrix can help with your Yield Management System implementation and integration.
You might also be interested in: