Industry News, Trends and Technology, and Standards Updates

EDA Testing – What Does the Problem Look Like for the Industry?

Anticipating and promoting the increased adoption of SEMI’s Equipment Data Acquisition (EDA / aka Interface A) standards, we’ve posted a number of blogs over the past 12 months to address questions that potential stakeholders have repeatedly asked across the value chain. These postings have dealt with everything from the factory applications enabled by EDA to the best practices for OEM implementation of these standards to the development of robust equipment purchasing specifications.

Since the adoption process has now clearly reached critical mass, we must seriously address the question “How are we going to test the equipment and systems that incorporate these standards?” in a way that supports the entire industry. It’s an excellent question, and one that has a multi-part answer.


Given the structure and expected use of the EDA standards, the acceptance testing process for a unit of semiconductor manufacturing equipment will include at least three components, each of which addresses a different aspect of the standards. Note that we’re explaining this from the perspective of the end customer in a semiconductor factory, since this is the most common use case, but most of the same principles apply when testing EDA client infrastructure/application components as well.

  • Compliance testing – does the equipment adhere to the specifications described in the SEMI Standards, and were these specifications interpreted correctly? Will it cleanly connect to the EDA client infrastructure without modification or extensive configuration?

  • Performance and stability testing – does the equipment meet the end users’ performance and availability specifications in terms of data sampling intervals, overall data volume transmitted, size and number of DCPs (data collection plans) supported, demands on the computing/network resources, up-time, etc.? Will it support the range of application clients expected in a production environment?

  • Equipment metadata model conformance testing – does the equipment model delivered with the interface represent the tool structure and content anticipated by the end customer? If the customer has requested that SEMI E164 (EDA Common Metadata) be fully supported, does the metadata model meet these specifications?

Of course, in addition to the requirements dictated by the standards themselves, most advanced semiconductor manufacturers will have a number of factory-specific requirements that must also be supported by the EDA interface. These may include special events and data for particular automation schemes, vectors of process parameters to support fault detection applications or other feature extraction algorithms, synchronization signals for external sensor integration, and the like. To address these requirements efficiently, an EDA test system should be extensible by its users.

You can see how interesting and vital this topic becomes when you consider the range of requirements outlined above. We’ll explore each of these in more detail in the next few postings, so stay tuned!


Topics: Industry Highlights, EDA/Interface A, EDA Testing Series

Posted by Alan Weber: Vice President, New Product Innovations on Oct 4, 2016 11:15:00 AM
Find me on: