Test applications
Products & services / Test applications
SECS/GEM and SEMI automation standards testing
We offer a range of products used by OEMs and factories to test different aspects of SECS communication on semiconductor equipment, including SEMI automation standards compliance, protocol testing, and scenario testing. Consult the table below to determine which PEER Group test application best serves your needs.
| Features | CCS Envoy™ | SECSIM Pro®+ | PFAT™ | DiDaCT 2 |
|---|---|---|---|---|
| SECS communication Enable SECS protocol communication between semiconductor equipment and factory automation systems. | ||||
| GEM compliance testing Testing that ensures compliance to the E30 SEMI Standard typically used in semiconductor backend manufacturing. | * | |||
| 300mm compliance testing Testing that ensures compliance to the suite of 300mm SEMI Standards (E40, E94, E87, E116, E90), typically used in semiconductor frontend manufacturing. | * | * | ||
| Test reporting Reporting of test results, either immediately after running a test or for historical reporting. Used to share test results within an organization or between organizations, e.g., OEM sharing test results with a factory source inspection team. | ||||
| Dynamic logic flow (parameterization) The ability to adjust the behavior of a test by altering the values of input parameters. | * | |||
| Scenario testing Testing that exercises complete production use cases such as remotely running a lot or uploading a set of recipes. | * | * | ||
| Runtime test inputs (e.g. carrier content map, etc.) The ability to supply test input parameters interactively as a test script runs. | * | * | ||
| Scripting Automatically execute multiple logical test steps in a sequence. | ||||
| Scripting without code Create scripted tests in a graphical environment without requiring development expertise. | ||||
| Extensible tests The ability to extend pre-defined tests or create new tests based on a set of testing activities/operations. | ||||
| Lights-out test environment The ability to execute tests without user intervention or a user interface. | ||||
| Integration with other software (e.g. hardware simulation) Multi-protocol communication to enable interfacing with orchestration of other software that is useful in a testing environment, e.g., hardware simulation. | * | |||
| Debug / step test scripts The ability to execute a test script interactively as part of test script development. | * | |||
| Extensible activities/operations The ability to extend the base set of testing operations with additional operations that are specific to either a piece of equipment or a factory scenario. |
*Partially supported