Industry News, Trends and Technology, and Standards Updates

Note: this will be the last blog published on cimetrix.com. For all future blogs, please visit our blog on PDF Solutions website.

Background

The SEMI North America, the Information & Control Committee meets three times per year, but this year the schedule is changed due to the SEMICON West  biennial  relocation to Phoenix beginning this year. SEMI held summer meetings in North America on June 2-4 at SEMI headquarters in Milpitas, CA. Like usual, the meetings are hybrid where attendees can join in person or remotely. The first two days are task force meetings including the GEM 300, ABFI (Advanced Backend Factory Integration), GUI, CDS (Fab & Equipment Computer & Device Security ) and DDA (Diagnostics Data Acquisition) task forces with Cimetrix task force leaders. The third day is the committee meeting where final decisions are made (usually) based on task force recommendations. This is a summary of what happened in some of the task forces and the committee meeting.

Note that all ballots that pass in the committee are still subject to a final review by the global SEMI Audit & Review committee, where a ballot technically can still fail when proper SEMI procedures and regulations are not strictly followed. This is rare in the North America Information & Control Committee but can happen and has happened.

A SNARF is a Standards New Activity Report Form. Before a task force can submit a ballot proposing a new standard or to modify an existing standard, the SNARF for this work must be approved by the technical committee.

Note that SEMI publishes a website with all global committee information where anyone can peruse the extensive details. It is at this website: https://www.semi.org/en/products-services/standards/developing-technical-standards.

Leadership Changes

Several leadership changes were approved during these meetings. For the last several years, Brian Rubow has been vice-chair of SEMI North America (NA) RSC Organization. During the NARSC meeting, Brian was nominated as co-chair. Alan Weber was nominated as co-leader of the Equipment Data Publication task force and co-leader of the Fab & Equipment Computer & Device Security Task Forces.

GEM 300 Task Force
Several weeks prior to meeting, Brian submitted a SNARF to the GEM 300 task force members for review. The SNARF proposes developing a new standard that enables secure GEM interface communication using gRPC technology and TLS. The new standard would be an alternative to the existing SECS-I and HSMS protocols used today. Neither of today’s protocols are secure and therefore present a cybersecurity risk. Feedback on the proposed SNARF indicates clear approval that we need a secure GEM protocol. However, the means to achieve security is still up for debate. Alternatives to gRPC offered by task force members include HTTP/2, WebSockets and secure TCP/IP communication. We discussed this a little at the task force meeting and plan to start meeting regularly to discuss and debate the alternatives until a technical solution is selected. We also decided to postpone approving any SNARF for this work until we decided on a technical direction. The addition of a secure protocol will be the big improvement to the GEM standard. Anyone interested in this topic should join the North America GEM 300 task force. The task force approved to work on ballots to modify the well-known implementations in four standards, E30 (GEM), E40 (Process Job Management), E87 (Carrier Management) and E90 (Substrate Tracking). In GEM, we wish to clarify the well-known naming for the Processing State Model collection events. Since every equipment can implement a unique Processing State Model tailored to its operation, the number and name of the Processing State Model collection events vary. We expect each of these ballots to be relatively small. The task force is also working on another ballot (7345) for the E90 (Substrate Tracking) standard related to batch processing. The current E90 standard is unclear how to report when batches are assembled and disassembled. The batch location state model has contradictions between the batch location states OCCUPIED and UNOCCUPIED and the transition tables. The ballot proposes a solution to the contradiction and additional collection events for batch assembly and disassembly. This ballot is ready for review by task force members and will be submitted for voting in the next voting cycle.

DDA (Diagnostics Data Acquisition) Task Force

The DDA task force remains very active while trying to finalize the EDA (Equipment Data Acquisition/Interface A) freeze 3 standards. All activities are focused on this goal. Ballot 7321A proposes changes to the core EDA standards, E120/E120.2, E125/E125.2, E132/E132.2, E134/E134.2 and E179. This ballot intends to be the final ballot for Freeze 3 for these core standards. It introduces one new feature, filtering E125 metadata to allow clients to request a subset of the equipment metadata when calling GetParameters, GetExceptions, and GetSimpleEvents. The other proposed changes reflect issues raised by task force members. These issues were raised either during the last vendor test session or since then as software development teams implement EDA Freeze 3 software. Both line items in the ballot failed and will be reworked for voting in Cycle 7 and adjudicated at SEMICON West in October. By failing the ballot, we can resolve the issues reported in ballot 7321B and resolve a few more issues reported since ballot 7321A was submitted. The final piece to EDA Freeze 3 is an update to the E164 standard (Specification for EDA Common Metadata). This ballot also failed and will be reworked for the next voting cycle. When these ballots (7321 and 7180) are approved and published by SEMI, we expect EDA Freeze 3 to be complete. Then we will modify standard E178 (Guide for EDA Freeze Version) to officially declare the EDA Freeze 3 version. In addition to this work, the DDA Task Force is also working on subordinate standards to E164. Each subordinate standard will standardize EDA metadata for one GEM-based standard, standardizing how to implement that standard in an EDA interface. The subordinate standard for E40 (process job management) is nearly ready for task force review. This work is outside the scope of EDA Freeze 3, only applicable when you implement the respective standard, but still directly related to EDA Freeze 3. This constitutes the bulk of remaining work.

ABFI (Advanced Backend Factory Integration) Task Force

The ABFI task for approved a SNARF to work on E142 to resolve some editorial changes and to add well-knowns to the subordinate standard E142.4. The task force is also working on a ballot to update the recently published E192 Guide for Equipment Adoption Criteria for GEM and GEM-Related Standards. Since this guide was published, two new standards related to GEM were published including the new Cybersecurity standard E191 and a new equipment data publication standard E190. This ballot has been submitted to the task force for review and will be submitted to SEMI in the next voting cycle.

CDS (Fab & Equipment Computer & Device Security) Task Force

SEMI standard E191 Specification for Computing Device Cybersecurity Status Reporting was published less than a year ago. The current version requires a GEM interface to publish two status variables to identify operating system information about the equipment’s factory facing computers. One identifies the computers, the other identifies the operating system manufacturer, name, version and build information. This helps factories identify cybersecurity risks within the factory and request upgrades. Ballot 7311A proposed to enhance the E191 standard by publishing additional information, introducing two additional status variables. One identifies the list of installed updates. The other identifies installed operating system components. This ballot passed and now awaits review by the Audit & Review committee before publication.

Next Steps

The North America Information & Control Committee will use SEMI voting Cycle 7 for the next round of ballots. Ballots are due to SEMI by Thursday, July 24 2025. These ballots will be adjudicated at SEMICON West October 6-8 at the Phoenix Convention Center.

Background

The SEMI North America, the Information & Control Committee meets three times per year, but this year the schedule is changed due to the SEMICON West semiannual relocation to Phoenix beginning this year. SEMI held winter meetings in North America on February 24-26 at SEMI headquarters in Milpitas, CA. Like usual, meetings are hybrid where attendees can join in person or remotely. The meetings include task forces with leaders from Cimetrix on the GEM 300, ABFI (Advanced Backend Factory Integration), GUI, and DDA task forces as well as the committee meeting on Wednesday. This is a summary of what happened in the task forces including GEM 300, ABFI and DDA and other task force activities. There were few ballots this last cycle, but I will also include updates from the Fall meetings in 2024 since I did not create a blog for those meetings.

Note that all ballots that pass in the committee are still subject to a final review by the global SEMI Audit & Review committee, where a ballot technically can still fail when proper SEMI procedures and regulations are not strictly followed. This is rare in the North America Information & Control Committee but can happen.

I also wish to note that SEMI publishes a website with all global committee information where anyone can peruse the extensive details. It is at this website: https://www.semi.org/en/products-services/standards/developing-technical-standards.

GEM300 Task Force

The most recent changes to the GEM and GEM 300 standards include the addition of ‘well-known’ names for all required collection events, alarms, data variables, status variables and equipment constants within each standard. Recent ballots are related to fixing a few errors in these new tables and updates based on other ballots. This work is finally done for the core standards. Next step in this long process is to update the EDA (Interface A) E164 standard and new subordinate standard to require use of these well-knowns and also to update the SEMI E172 SEDD standard to require use of the well-known names in equipment SEDD files. This has taken a couple years to develop, but ultimately will be extremely useful to quickly map host software applications to implementations, both for EDA and GEM interfaces, and to identify GEM data in EDA implementations. Quicker mapping means quicker equipment integration at the factory.

Last fall, the GEM 300 task force passed some minor updates to the E90 substrate tracking standard in ballot 7278. This includes adding a couple new variables related to the substrate attributes not previously called out specifically yet were added more for completeness than usefulness. This winter, another E90 ballot 7316 passed that corrected a long existing spelling inconsistency for variables between E90 and E90.1. This should not affect implementations, yet some implementers may wish to rename a couple of variables in their implementations to match the standard.

Last fall, the GEM 300 task force made similar changes to the E87 carrier management standard in ballot 7279. In addition to adding a few new well-knowns mapping to additional port and carrier attributes, the well-known names for alarms now support port specific alarms. Well-known names were added for the Carrier Complete Prediction state model, recently updated in 2024 with significant changes. Finally, the carrier’s substrate count attribute format was modified from a limiting 1-byte to allowing 4-byte implementations. This is an important improvement for the semiconductor backend industry where there can be hundreds of substrates on a carrier, unlike semiconductor front end where the substrates are typically wafers and limited to 25.

This winter an E157 Module Process Tracking ballot finally passed in its third attempt. This ballot significantly enhanced to support equipment that don’t have a process chamber. The current published standard focuses on reporting recipe execution in a process module, where all the material in the chamber is processed simultaneously. Most importantly, the standard enables reporting when each step in the recipe begins and completes. Many equipment in especially outside of semiconductor front-end don’t have a process module and instead have continuous flow operation. The enhancements to E157 enable reporting the recipe execution on a specific substrate, including when each step begins and completes. This is another example how GEM related standards are adopting to the needs of backend equipment.

Ballot 7312 replaced ballots 7275 and 7276 from the 2024 fall meetings to implement well-known names in SEMI E5, the SECS-II standard. The task force decided to rename E30 well-known names that originate in SEMI E5 with an ‘E5’ prefix instead of ‘E30’. This passed ballot completes the current plans to develop these well-known names in the GEM related standards.

DDA Task Force

Last fall, the DDA task force pass just one ballot. Ballot 7288 resolved a few issues raised by task force members and an update the .proto files to align with the current Protocol Buffers Style Guide. By conforming to the Protocol Buffers Style Guide, gRPC code generators can better adapt to language specific styles.

After the DDA task force met last fall, a group of companies volunteered to test the data collection features using the proposed gRPC interface definitions and updated E134 standard. Previous test sessions had already validated E132 Session Management and E125 Equipment Modeling. A test plan was created and previously distributed to the participants. Attendees alternated connecting with each other’s software as clients and servers and then collecting data. Five companies participated. Twenty-eight issues were submitted of varying severity. Based on this feedback, the DDA task force created ballot 7321 to correct known issues. Since then a few more issues have been reported. The task force ballot failed one of the ballot line items and will resubmit with corrections and a few additional changes for voting in the upcoming cycle. If all goes well, the changes in ballot 7321A will become the core of the EDA Freeze 3 standard. We can hope!

The DDA Task Force is also actively developing a ballot to update SEMI standard E164 which establishes EDA equipment modeling guidelines. New subordinate standards will map GEM 300 standards to a specific EDA freeze 3 implementation based on the well-known items recently defined in the GEM 300 standards and based on the updated primary standard E164 guidelines. This is the final piece to establishing a complete EDA Freeze 3 standard. Client and equipment server implementers can develop software before E164 is finalized.

ABFI (Advanced Backend Factory Integration) Task Force

No ballots were adjudicated in the ABFI task force. Instead, the task force continued several open discussions. We discussed how a ballot from last year was published as a new standard SEMI E192 Guide for Equipment Adoption Criteria for GEM and GEM-Related Standards. The guide was just published in January 2025 and aims to provide a high-level overview and organization of the 40+ GEM related standards and the GEM related 30+ subordinate standards. The guide is meant to introduce the many GEM related standards for newcomers and experts alike. Since the guide was written and now published, several developments have occurred which require the guide to be updated.

• The Computer and Device Security task force in the Information & Control Committee developed a new GEM-related standard, E191.
• The GEM 300 task force expanded the scope for E157 including a title change.
• The Equipment Data Publication task force in the Information & Control Committee developed a new GEM-related standard, E190.

A new ballot was approved to update the SEMI E192 guide with these latest changes.

Additionally, the ABFI task force is planning to update the SEMI E142 substrate map specification to include standardized XY coordinate system mapping.

CDS (Computer & Device Security) Task Force

The CDS task force is actively updated SEMI standard E191, the Specification for Computing Device Cybersecurity Status Reporting. This new standard defines standard status variables on a GEM interface regarding the operating system for each computer in the equipment, such as the name, version and build of the operating system. This enables factories to track the operating systems on the computers and compare this with any known vulnerabilities and request equipment computer patches and upgraded. The standard will be updated to provide more information, although the additional data is not yet completely decided.

Information & Control Committee

A new order of business was introduced in the Information & Control Committee by representatives from the Physical Interfaces and Carriers committee. Our two committees share control of the SEMI standard E84 the Specification for Enhanced Carrier Handoff Parallel I/O interface. Some users are interested in developing a new TCP/IP based protocol be introduced to replace the parallel I/O interface. The discussions are preliminary just seeking interested parties at this time.

To learn more about the SEMI standards, the committees or just to speak with an expert please click the button below. 

Background

The SEMI North America Information & Control Committee meets three times per year; spring, summer and fall. This year the spring meetings were held on March 25, 26, and 27 at SEMI headquarters in Milpitas, CA. The meetings include task forces with leaders from Cimetrix on the GEM 300, ABFI (Advanced Backend Factory Integration), GUI, DDA, CDS task forces as well as the committee meeting, held on Wednesday. This is a summary of what happened in the task forces I am highly involved in, including GEM 300, ABFI and DDA. There were few ballots this last cycle, especially compared to the last meetings.  

Note that all ballots that pass in the committee are still subject to a final review by the global SEMI Audit & Review committee, where a ballot can still fail when proper SEMI procedures and regulations are not strictly followed. This is rare in the North America Information & Control Committee but can happen. 

GEM 300 Task Force

Ballot 6836A was modified to address issues raised by several voting members at the fall meetings. In this round of voting, the ballot passed with no rejecting votes and some minor comments from me. Ballot 6836A modifies both specifications E87 Carrier Management and E90 Substrate Tracking. In Substrate Tracking, the substrate object now defines a new optional attribute, “AdditionalInfo”. This attribute is used to designate a list of name/value pair information to be used as needed. The existence of the attribute is standardized, but the usage and values for the names in the name/value pair are custom to be used as needed. For example, an equipment handling multiple substrate types can use a name/value pair to distinguish between the different substrate types. In Carrier Management, carrier objects now define a related new optional attribute “AdditionalSubstrateInfoMap” to store the list of name/value pair information for all substrates in a carrier. These new features enable GEM 300 like E90 and E87 standards to be more easily adapted to all types of equipment and applications.

The Japan GEM 300 task force has proposed ballot 7173 to make minor improvements to the text in the GEM E30 standard. The proposed changes have been submitted to other regions including North America for review. None of the changes are technically significant and should not affect existing GEM implementations.

A few new ideas for ballots were also discussed at the task force. Following are some details on two items that were discussed.

The most prominent new discussion proposes changes to the E157 Specification for Module Process Tracking. Currently, adoption for this standard is limited to equipment that have one or more well-defined or virtual process modules. There are many types of equipment outside of Semiconductor Front-End that do not have a clear concept of a process module like equipment with conveyors moving substrates through the equipment. The new ballot would propose modifications to E157 to define a new, similar state model that can be adapted to report processing details for a substrate rather than a process module. This continues a trend at SEMI to make changes to allow for easier GEM adoption in other industries and more types of equipment.

Another ballot proposes some changes to the new ‘well-known’ subordinate standards to the GEM and GEM 300 standards that establishes standardized names for the alarms, data variables, collection events, status variables and equipment constants required by these standards. While these new subordinate standards have not yet been published, a couple changes are under consideration soon once they are published.

DDA (Diagnostics Data Acquisition) Task Force

• Ballot 7174 was approved to update E128 Specification for SML Message Structures with language to include Transport Layer Security (TLS) because Secure Sockets Layer (SSL) has been deprecated by the Internet Engineering Task Force (IETF). E128 is a key standard in Equipment Data Acquisition communication freeze 1 and 2.
• Ballot 7175 was proposed to update E132 Specification for Equipment Client Authentication and Authorization and the E132 gRPC implementation with several issues found while preparing for EDA Vender Test #2.
  • Line item #1 introduced the most significant change; a modification to the password hash algorithm to be a binary array instead of a string. A binary array is more appropriate due to the software hash functions available to programmers. This line item failed due to a technical error in the ballot. The line item will be reworked to resolve this technical mistake and other errors that were revealed later in the week during EDA Vender Test #2.
  • Line item #2 moves some requirements from E134 to E132 in cooperation with ballot 7176. This ballot adds the requirements to E132 and passed.  
• Ballot 7176 was approved to move requirements from E134 Specification for Data Collection Management to E132 in cooperation with ballot 7175 line item #2. This ballot removes the requirements from E134. 
• Ballot 7191 approved changes to E179 Specification for Protocol Buffers Common Components. The ballot primarily introduces some optimizations to the protocol buffer usage to avoid sending parameter type information twice. This affects both ParameterValueType and ArrayParameterValue in the protocol buffer implementation. The changes also clarify the handling of 1, 2 and 4-byte integers by separating into unique types in E179. 
• A software vender test #2 was held on the day following the North America Information & Control Spring meetings. Anyone implementing client and/or server software was invited to attend. Instead of testing for standard compliance, the purpose of the vender test was to test interoperability and flush out any remaining issues in the EDA freeze 3 standards. This software vender test session #2 focused on previously untested E132 features from software vender test session #1 and will also include E125 tests. Several companies including Cimetrix attended the vender test session, providing both client and server functionality for testing against each other. Although official results of the test have not yet been made public, the primary issue discovered is that the password hash algorithm needs to be clarified. 
• A software vender test session #3 will be held either immediately following the North America Information & Control Summer meetings held in conjunction with SEMICON West in July, or after the Fall meetings in November. This test session will focus on E134 testing. Mid-April the task force will decide when to proceed.
• Future ballots were proposed for E125, E134, and E179 without specific known issues. In addition to the open ballot for E132, the task force can handle making any last minute changes to the EDA standards before EDA freeze 3 is declared.

ABFI (Advanced Backend Factory Integration) Task Force

No ballots were adjudicated in the ABFI task force. Instead, the task force conducted several open discussions. 

• A ballot has been approved to proposed modifications to E90 Specification for Substrate Tracking to accommodate equipment that have multiple substrate ID readers. Currently E90 assumes that an equipment only has one type of substrate and therefore one substrate ID reader. As the GEM 300 standards are implemented on more backend equipment, issues like this are revealed and need a standardized resolution.
• A previous proposal, 6840, to create a Specification for Equipment Adoption Criteria for GEM and GEM-Based Standards was cancelled. In its place a new proposal was approved to create a Guide for Equipment Adoption Criteria for GEM and GEM-Based Standards. A guide differs from a specification because it does not include any requirements. The new guide will help anyone implementing GEM technology understand how the vast number of GEM related standards fit together and when they should be used.
• A new activity was introduced to consider handling substrates with topside and bottom-side identification. More to come as the task force investigates this further. 
  
  

SEMICON West 2024

The next North America Information and Control meetings will be held in conjunction with SEMICON West in San Francisco. The dates will be July 9-11, 2024. Due to the association with SEMICON West, these meeting typically have the most in person attendees.

Background

The SEMI North America, the Information & Control Committee meets three times per year; spring summer and fall. This year the fall meetings were held on November 6, 7 and 8, 2023 at SEMI headquarters in Milpitas, CA. The meetings include task forces with leaders from Cimetrix on the GEM 300, ABFI (Advanced Backend Factory Integration), GUI, DDA, CDS task forces as well as the committee meeting on the final day which was held on Thursday instead of the typical Wednesday. This is a summary of what happened in the task forces I am highly involved in including GEM 300, ABFI and DDA. The recent voting cycle included 22 ballots—the most ballots in one voting cycle that we have seen for a very long time.  

Note that all ballots that pass in the committee are still subject to a final review by the global SEMI Audit & Review committee, where a ballot can still fail when proper SEMI procedures and regulations are not strictly followed. 

GEM 300 Task Force

A lot is going on the GEM 300 task force. The following SEMI standards were reapproved: E39 and E39.1. Reapprovals occur every 5 years else a standard becomes inactive.  

Ballot 7066A proposed changes to the SEMI E87 Carrier Management Services (CMS) standard. This ballot failed previous voting, but now time passed as a ‘superclean’ ballot (no negatives or comments during voting). This ballot included a significant change to the Carrier Ready to Unload Prediction feature which is now called a Carrier Complete Prediction. Anyone who implemented Carrier Ready to Unload Prediction will have to make a lot of changes to comply with the new implementation. A primary driver for this change is to accommodate internal buffer equipment where the READY TO UNLOAD state depends on when the host sends a CarrierOut message and the queue of previously requested activities; therefore, not a useful prediction to make. 

The benefit of this new state model is to notify the factory host before a carrier is completed so that the automatic delivery can be scheduled to arrive for pickup when the carrier is ready. This can shorten the time it takes for the factory to move material from one equipment to the next. 

Seven similar ballots 7114, 7115, 7116, 7117, 7118, 7119 and 7120 were submitted respectively for standards E5/E30, E40, E87, E90, E94, E116 and E157 to define a ‘well-known name’ for each require collection events, variables and alarms. The ‘well-known’ names are aliases for mapping purposes; necessary because each implementation can use different names. The ultimate goal of this feature is to make the GEM and standards based on GEM more plug-and-play. This new feature serves at least two purposes. Standard E172 already defines a well-known name attribute in the SECS Equipment Data Dictionary (SEDD) file. In the Equipment Data Acquisition (EDA) standard freeze 3 version, E164 will use this well-known name as well. The regular GEM documentation can also reference the well-known name. To explain the value of this feature, E90 requires a collection event for Substrate Location State Model transition 1. Implementers might define this collection event using any name such as E90_Loc_Unoccupied2Occupied, SLTrans1, SubstrateLocationUnoccupiedToOccupied or CollectionEvent901. Any name is allowed. The new well-known name establishes a standardized alias name called the well-known. 

When ballot 7117 is published, the well-known name table establishes well-known name “E90:SubstrateLocation:001:Unoccupied-Occupied” as the standardized alias for this collection event. This SEDD file can be downloaded through the GEM interface, tell the GEM host exactly which collection event implements the Substrate Location State Model transition 1. During the Information & Control Committee, ballot 7117 resulted in a Ratification ballot handling a long existing E90 naming issue for one status variable. All of the other ballots passed with a simple editorial change. 

A few of the above well-known name ballots included additional line items to resolve issues in the respective standard, mostly editorial or minor. Ballot 7114 included an E5 clarification that Stream 21 Function 17/18 sequence can be aborted by the receiving entity with an S21F0 message. Ballot 7116 included several additional changes/corrections to E87. 

1.    Clarification on the CARRIER SLOT MAP STATUS state SLOT MAP VERIFICATION FAILED, which sometimes was spelled in E87 without the ‘ED’ in FAILED. 
2.    Corrections to Table R1-21 in the table heading.

3.    Carrier object attribute Capacity can now be format code 51, 52 or 54, increasing the allowed carrier size from 255 to 4.29 GB to accommodate carriers not holding wafers but smaller substrates. 
4.    Carrer state model transition 7 includes a new trigger as already described scenario R1-21. 
5.    Scenario R1-20 was reverted to its original design, undoing an error introduced in 2012

6.    And finally, equipment constant BypassReadID was added to E87.1. This equipment constant has been defined in E87 but missing in E87.1

Ballot 9836 proposed some synchronized changes in E87 and E90 to define new name/value pair attributes. The ballot failed due to some limiting details in the value format definition. The ballot intends to allow equipment and factory to agree to using additional substrate content and characteristic information.

The Japan GEM 300 task force is working on improving the GEM E30 standard. The task force proposed a number of minor improvements mostly editorial to clean up several areas with the specification. Although the work was originally proposed to occur in the North America group, the task force decided to handle this ballot in Japan who will meet in December of 2023. Of course, the regional GEM 300 task forces worldwide all share and vote together on all E30 ballots.

DDA (Diagnostics Data Acquisition) Task Force

The DDA task force reapproved three standards: E128, E138 and 145. Additionally, the DDA task force made more plans to complete the Equipment Data Acquisition (EDA) freeze 3 version. Here are the key activities and findings as of today:

• E164 will be modified to incorporate the well-known names from the GEM 300 force. Instead of including all GEM 300 standards directly in the E164 primary standard, each GEM 300 standard will have a smaller, simpler E164 subordinate standards (E164.1, E164.2, …) to define the EDA implementation for that standard. This strategy makes adopting EDA and E164 more flexible to use in industries beyond semiconductor front end equipment.
• Some errors were found in the published .proto files for E132 and E134. New ballots will be submitted as soon as possible to make corrections.
• A software vendor test #2 will be held immediately following the North America Information & Control Spring meetings. Anyone implementing client and/or server software is invited to attend. Instead of testing for standard compliance, the purpose of the vender test is to test interoperability and flush out any remaining issues in the EDA freeze 3 standards. This software vender test session #2 will focus on previously untested E132 features from software vender test session #1 and will also include E125 tests. Anyone interested in joining should contact me (Brian Rubow) or Albert Fuchigami (Brian’s co-leader). Prior to the software vender test session, the task force co-leaders will provide a test plan document and .proto files with corrections in E132 for known issues.
• A software vender test session #3 will be held immediately following the North America Information & Control Summer meetings held in conjunction with SEMICON West. This test session will focus on E134 testing. 

ABFI (Advanced Backend Factory Integration) Task Force

Ratification ballots R2924A and R6925A both passed. This means that the new Consumables and Durables standard is in the SEMI publication queue. 

Additionally, ballot 6948 passed with several great improvements to the E142 substrate mapping standard. The improvements should help users better understand how to use the E142 schema files for more consistent adoption by implementers. 

Spring 2024

The next North America Information and Control spring meetings will be held again at SEMI headquarters in Milpitas, California. The dates will be March 25-27, 2024. Although many attendees were remote during these meetings, I expect many more attendees to be in person at these spring meetings due to the EDA software vender test session.  

To learn more about the SEMI Standards and the work we do as members of SEMI, please click the button below.

Background

At SEMI in North America, the Information & Control Committee meets three times per year; spring summer and fall. This year the summer meetings were held on July 10, 11 and 13 in conjunction with SEMICON West is San Francisco, CA. The meetings include task forces with leaders from Cimetrix on the GEM 300, ABFI (Advanced Backend Factory Integration), GUI, DDA, CDS task forces as well as the committee meeting on the final day which was held on Thursday instead of the typical Wednesday. This is a summary of what happened in the task forces I am highly involved in including GEM 300, ABFI and DDA as well as some updates from SEMI.

Note that all ballots that pass are still subject to a final review by the global SEMI Audit & Review committee, where a ballot can still fail when proper SEMI procedures and regulations were not strictly followed.

SEMI

A few changes are happening at SEMI. SEMI is planning to start publishing ‘red-line’ versions of the SEMI standards. Today, when a new version of a SEMI standard is published, it includes change bars on the side to indicate where changes have occurred. The changed section can then be compared with the previous publication to see what changed. While this is helpful to readers, the planned ‘red-line’ versions will identify precise changes using redline strikethrough and underlining to identify the changes. This is a big benefit to the standards community. I look forward to seeing this new feature.

SEMI is planning to add additional digital enforcement to the SEMI standard documents to help enforce SEMI’s copyright to the standards. This should help curb some of the copyright abuse. Every company implementing or using the SEMI standards should have at least one subscription to SEMIViews, https://www.semiviews.org/.

SEMI has hired another technical writer to help keep SEMI standard publication up to date. Recently, the growing queue of standards awaiting publication has affected SEMI standards development. For example, this has caused delays in the DDA task force developing EDA Freeze 3. In the last 9 months, SEMI has already reduced the publication queue substantially and is committed to catching up early in 2024.

GEM 300 Task Force

A lot is going on the GEM 300 task force.

Ballot 7065, an update to the SEMI E172 passed nearly super-clean. SEMI E172, SPECIFICATION FOR SECS EQUIPMENT DATA DICTIONARY (SEDD) defines the XML schema for documenting a GEM interface. Recently the GEM standard was updated to allow transfer of a SEDD file through the GEM interface using Stream 21 messages. Ballot 7065 adds a few new features and changes to the schema files. The most important changes are names for alarms and a ‘well-known’ element to all collection events, variables, and alarms. This ‘well-known’ element is meant to contain a standardized alias so that end users can automatically map an implementation to required items in the SEMI standards. To capitalize on the new E172 ‘well-known’ feature, new ballots were approved to modify E5/E30, E40, E87, E90, E94, E116 and E157 to include standardized ‘well known’ names. These ballots are expected to be completed in time for cycle 7 voting this year.

Ballot 7066 proposed changes to the SEMI E87 Carrier Management Services (CMS) standard. This included a significant change to the new Carrier Ready to Unload Prediction feature. The primary driver for this change is to accommodate internal buffer equipment where the READY TO UNLOAD state depends on when the host sends a CarrierOut message and can be drastically impacted by the carrier-out queue. The ballot proposes to use CARRIER COMPLETE prediction instead, which can be universally applied both fixed buffer and internal buffer equipment. The change has little impact on fixed buffer equipment, where the time between CARRIER COMPLETE and READY TO UNLOAD is typically short and a fixed time. Unfortunately, this line item in the ballot needs some rework before it is ready for acceptance.

The other line items in ballot 7066 passed including a clarification to the ContentMap behavior and an update to the CMS compliance statement. Two requirements related to the ContentMap were in contradiction to each other affecting the ContentMap value when a carrier object is instantiated. The clarification allows the ContentMap to either be an empty list or a structured list of empty lot and substrate ID information. The change only affects the initial value. The compliance statement change adds the missing “Access Mode State Model” to the compliance statement so implementers can declare whether this feature is implemented and compliant.

Ballot 6991 also passed as super-clean (no negative votes) to update SEMI E4 SEMI Equipment Communications Standard 1 Message Transfer (SECS-I). The update removes biased terminology to be compliant with recently updated SEMI regulations. No technical changes were made.

ABFI (Advanced Backend Factory Integration) Task Force

New proposed standards for Consumables and Durables (ballots 6924A and 6925A) both will require Ratification ballots. This means that a few technical changes need to be made for the new standards to be accepted. Ratification ballots R6924A and R6925A will be submitted in the next voting cycle with those technical changes. If this passes, then the new standards will be published. If it fails, then the ballots will be reworked for another voting cycle.

DDA (Diagnostics Data Acquisition) Task Force

The DDA task force meeting was relatively quiet and uneventful for the first time in years while the task force waits for accepted ballots to be published including updates to E125/E125.2, E134/E134.2, and E120.2. No ballots were adjudicated. Ratification ballot R7002 for SEMI standards E132 and E132.2 passed in the voting cycle 4. Meanwhile new versions of E121 and E179 were published by SEMI in April and June, respectively.

Next steps for the DDA task force include updating E164 and planning a ‘vendor test session’. The E164 update is tied to the GEM 300 ‘well-known’ feature mentioned above, where the E164 names and IDs will be synchronized with the aliases added to the GEM 300 standards. The vendor test session is planned to occur during Spring 2024. Any company wishing to participate to validate EDA client or server software against other implementations is welcome. Participants will run through a small set of E132 scenarios, E125 scenarios and E134 scenarios to validate the current standards. Any issues found during this testing will be quickly resolved so that an EDA freeze 3 version can finally be declared. The task force leaders plan to share a test plan before Fall meetings to help everyone prepare.

Background

At SEMI in North America, the Information & Control Committee meets three times per year; spring summer and fall. This year the spring meetings were held on April 3-5. The meetings include task forces with leaders from Cimetrix on the GEM 300, ABFI (Advanced Backend Factory Integration), GUI, DDA, CDS task forces as well as the committee meeting on the final day. This is a summary of what happened in the task forces I am highly involved in including GEM 300, ABFI and DDA. 

GEM 300 Task Force

After very busy previous GEM 300 task force meetings over the last couple of years, this is the first time in a long time that the GEM 300 task force did not have a major ballot up for voting. A major update to the GEM standard (SEMI E30), ballot 6572C, is awaiting publication at SEMI but was previously approved. In our task force meeting this week, we primarily discussed a new ballot proposed by a couple of active task force members regarding SEMI E172, SPECIFICATION FOR SECS EQUIPMENT DATA DICTIONARY (SEDD). The proposed new ballot would enhance the E172 SEDD file to add: 

1. alarm names
2. a new “well known” element to all collection events, data variables, status variables, equipment constants and alarms.
3. enhanced comments in the schema file
4. possibly a few schema changes regarding the handling of empty lists

The major new feature is the “well known” element. When an equipment supplier creates a GEM interface on the equipment and related GEM 300 standards, the implemented SEMI standards define required collection events, data variables, status variables, equipment constants and alarms which much be available. However, the actual name for each required item published in the GEM interface is not specified in the standard and is not a strict requirement. As a result, implementations of GEM and GEM 300 standards use different names for the same required item. For example, the GEM standard requires collection event “Control State REMOTE” to notify when the operator changes the equipment to remote control. One implementation might call this collection event “ControlStateRemote” while other implementations might call this collection event “Control State REMOTE” or “CntrlStateREMOTE”. All of these names are valid and GEM Compliant. The “well known” element in the E172 SEDD file would allow items in the GEM interface to be assigned a tag mapping it to a required item in a SEMI standard. Each SEMI standard in turn will need to be updated to define “well known” names to use in the E172 SEDD File. This new feature will allow GEM host software to have increased plug-and-play intelligence when connecting to a GEM interface to identify standard features. EDA (Equipment Data Acquisition) interfaces solved this problem in the SEMI E164 standard. The proposed “well known” names to be used in a GEM interface are expected to use the same names currently found in SEMI E164. Then SEMI E164 can be updated to reference the same “well known” names. This will be a lot of work to standardize, but will be a valuable feature. The upcoming GEM revision already defines how an SEDD file can be transmitted through the GEM interface using Stream 21 messages. 

Additionally, the task force discussed SEMI E87 and the new carrier ready to unload prediction. Prior to these discussions on April 3, I had thought that the state model was stabilized enough to implement. However, the work for ballot 6835 has been redefined to include additional work to modify the state model yet again. With this redefined scope, a new ballot number will be issued by SEMI. The task force is investigating changing the state model to predict transition to a final carrier accessing state (carrier complete or carrier stopped) instead of predicting transition to the carrier ready-to-unload state. The assumption is that the time between carrier completion and ready-to-unload states is fixed, and that it might be more useful for internal buffer equipment to predict carrier completion instead than ready-to-unload. Additionally, a few of the states are proposed to be changed. 

Both activities are expected to happen quickly and be submitted for SEMI voting cycle 5 in 2023. 

ABFI (Advanced Backend Factory Integration) Task Force

A new specification (ballot 6924, Specification for Equipment Management of Consumable and Durables) and subordinate standard (ballot 6925, Specification for SECS-II Protocol for Equipment Management of Consumable and Durables) were submitted for voter feedback since the committee last met in the fall. During the Spring meetings, the voter feedback was adjudicated. The ABFI Task Force and the I&C (Information & Control) Committee agreed to fail ballots 6924 and 6925. There were a few technical mistakes in the ballots that need to be reworked. Most of the feedback identified editorial mistakes or improvements in the ballot. Only a few minor technical issues need to be ironed out. I will be reworking both ballots, seeking task force member feedback and submitting them to the upcoming SEMI Cycle 5 voting. The voting feedback from the last cycle makes me optimistic that the ballots will soon pass and become new standards. 

The task force also spent time discussing and debating SEMI E142 substrate maps and how they might be used in specific traceability situations. 

DDA (Diagnostics Data Acquisition) Task Force

The DDA task force and Information & Control committee pass several ballots proposed by the DDA task force including:

• Ballot 7001 – Revision to SEMI E125-1022 Specification for Equipment Self Description (EqSD) and SEMI E125.2-1022 Specification for Protocol Buffers for Equipment Self Description (EqSD)
• Ballot 7002 – Revision to SEMI E132-0922 Specification for Equipment Client Authentication and Authorization and SEM E132.2-0422e Specification for Protocol Buffers for Equipment Client Authentication and Authorization (ECA)
• Ballot 7003 - Revision to SEMI E134-1022 Specification for Data Collection Management and SEMI E134.2-1022 Specification for Protocol Buffers of Data Collection Management
• Ballot 7017 - Line Item Revision To SEMI E120.2-0922: Specification For Protocol Buffers For Common Equipment Model (CEM)

All of these ballots are part of the effort to develop a “freeze 3” version of the EDA (Equipment Data Acquisition) standards, where the underling protocol will use gRPC and Protocol Buffer technology instead of the current SOAP and HTTP seen in EDA freeze versions 1 and 2. 

Ballot 7002 includes multiple editorial changes and technical changes. The technical changes will result in a Ratification ballot for SEMI Cycle 4 voting. If the Ratification ballot passes, then ballot 7002 will pass. But if it fails then ballot 7002 will also fail and have to be reworked. 

While handling the considerable work adjudicating all of the ballot negatives and comments, the task force considered some new cases. For example, the task force discussed the role of the Security Admin, and whether it should be used only for EDA interface management as designed today or whether it should also provide additional EDA diagnostics capabilities. 

For the first time in a very long time, no DDA ballots are proposed for the next voting cycle (other than the Ratification ballot). The task force co-leaders are hoping to let SEMI publication catch up and to plan another event where companies can test EDA against other implementations. The previous tests were limited to E132. Since then some major changes have been made to E132. The new tests would include testing E132, E125 and E134 together to ensure that the standards define compatible and useful EDA implementations. After these tests, it is expected that one more round of changes might be needed for E132, E125 and E134 to correct defects or missing features identified by members participating in this testing. 

Information & Control Committee

For the first time in a very long time, the committee meeting was unable to complete all planned business. To comply with SEMI regulations, the meeting was required to end on time with unfinished business. The unfinished business will be handled by the Information & Control GCS chairs. This group includes the co-chairs from the SEMI Information & Control Committees in North America, Japan, South Korea, Taiwan and China. 

Background

The North America Information & Control Committee (I&CC or NA I&CC) is comprised of several task forces including GEM 300, Diagnostic Data Acquisition (DDA), Advanced Backend Factory Integration (ABFI), Fab & Equipment Computer and Device Security (CDS), and Graphical User Interfaces (GUI). These task forces and the committee all met during the week of SEMICON West, July 11-13, 202. Not long ago, SEMI regulations were modified to allow TC Chapter (Committee) voting in virtual meetings; therefore, the standards activities continue to move forward. In-person task force participation was much higher than the last meetings, but remote participation also remains strong. This blog is a summary of the activities in each task force.

GEM 300 Task Force

Here is a summary of worldwide activities related to the GEM 300 task force as of the start of the GEM 300 task force meeting.

 

Three ballots were adjudicated during the GEM 300 task force meeting. The term “adjudication” means we review the voting and recommend handling of all negative votes and comments received to ultimately accept the ballot for publication or reject the ballot for rework. The recommendations by the task force are then finalized at the committee meeting. Usually, the task force recommendation is accepted by the committee, as was the case in all three ballots.

6916 E5

This ballot proposes to modify the E5 SECS-II standard and included the following minor changes:

• Allow data variable OperatorCommand to be type ASCII.
• Correct various typographical errors
• Remove the dependency between variables MDLN (equipment model number) and EqpSerialNum (equipment serial number).

This ballot passed after the only negative was withdrawn by the voter.

6572B E30

This ballot proposes to modify the GEM (E30) standard. It is a revision ballot, meaning the entire E30 standard is subject to review. This is the third time the ballot has been submitted. It is a major update to the GEM standard and includes the following changes:

• Process Program Management changes
  • The terms “recipe” and “process program” are currently used nearly interchangeably. The proposal is to use the term “process program” exclusively.
  • References to E42, large formatted and large process programs are moved out of the main standard and into the appendix.
  • Stream 21 messages are introduced for process program management, including both the single and multiple message techniques. This provides a simplified way for GEM interfaces to upload and download large process programs.
  • The entire process program management section is vastly reorganized to help implementers understand the available alternatives and the scenarios for each available alternative. New tables were introduced to compare and summarize implementation alternatives.
  • Collection event ‘Process Program Error’ is specifically listed as required, rather than just as an implied requirement.
• A series of new SECS-II messages are introduced including S2F51-S2F64. These are new capabilities to make a GEM interface more transparent.
• S5F7/F8 is added to the alarm management capability for similar reasons.
• Two new GEM documentation features are added and made available through the GEM interface using Stream 21 messages including PDF documentation and SEDD (see SEMI E172) documentation. This should make it easier to distribute GEM documentation and ensure that the right documentation is referenced.
• Two new equipment identification features are added, one to identify the equipment supplier and one to uniquely identify each individual equipment. This should make it easier to identify and track specific equipment on the factory floor.
• Some changes related to terminology are included. SEMI regulations recently were updated with a list of restricted bias terminology which are not allowed in any SEMI standards and a list of terms to avoid when possible.

This ballot failed due to a disagreement regarding a proposed change to the GEM control state model collection on transition 10 related to the host off-line state. The task force remains evenly divided on this issue; therefore, this change will be withdrawn from the next revision of this ballot.

I am optimistic that the 6572C revision of this ballot will pass voting with little controversy. This ballot has already been distributed to the task force for final review. Little controversy remains unless some voter raises a new issue.

6859 E116

Originally ballot 6859 intended to add significant new features to the E116 standard. However, the aggressive changes have been abandoned. Instead, this ballot is focused on making one change to E116. Currently the E116 specification implements collection events in a manner inconsistent with E30, E40, E87, E90, E94, E109, and E157. This E116 ballot failed. After further discussion in the task force, consensus on the proposed changes seems possible in the next voting cycle. The updated ballot 6859A has already been submitted for review by the task force.

DDA Task Force

The DDA task force has been and continues to update the Equipment Data Acquisition (EDA a.k.a. Interface A) standards with the goal to approve an EDA Freeze 3 set of standards based on gRPC technology. To date the following ballots have been completed:

During these meetings, three DDA task force ballots failed adjudication, 6927 (E125, E125.2), 6928 (E132, E132.2) and 6929 (E134, E134.2) due to procedural errors which violated SEMI regulations. This is primarily due to a long backlog of publications on previously approved specifications. Discussions were held in several meetings in an attempt to find ways to help SEMI get caught up on publications. The delay in publication is partly due to the several large ballots that were backlogged when COVID activity prevented the committee from completing adjudication in remote or hybrid meetings.

Test Session #1

The most important activity for the DDA task force was “vender test session #1” held on Thursday, July 14. An open invitation was made to all task force members to participate in an E132 test session. Anyone could submit a client and/or equipment server implemented with the current E132 and E179 specifications. Four companies came together and ran tests against each other’s software. Each participant will provide the task force with a list of issues in E132 and E179. This was a great opportunity to try the gRPC technology together and get a sense of what issues still need to be resolved before EDA Freeze 3 is complete.

DDA Freeze 3 Plans

The DDA Task force plans an update to E125, E132, and E134 including changes from the recently failed ballots as well as topics raised in the test session. Due to the expanded scope, new ballot numbers will be issued. Additionally plans to update E164 are also moving forward. The biggest challenge for E164 will be converting the XML files into JSON files. Either JSON5 or JSONC will likely be used since comments are mandatory in the E164 complementary files which show how to create GEM 300 capable EDA equipment models.

ABFI Task Force

The Advanced Backend Factory Integration task force is actively working on two ballots.
One ballot is a minor update to the E142, the substrate mapping specification which facilitates traceability and other application where substrate, tray, feeder, and other information can be shared between a factory and equipment. The minor update will add additional substrate types so E142 substrate maps can be used in more applications.

Additionally, the task force is working on ballots 6924 and 6925. The 6924 specifications will define the management of Consumable and Durables on manufacturing equipment. Features include allowing the host to accept or reject newly mounted consumables and durables. Additionally, the equipment will be able to report on consumable and durable usage. While technically both can already be done, the specification establishes a standard way for the features to be implemented. The 6925 ballot maps 6924 for usage in a GEM interface. The plan is to submit the ballot for the next voting cycle.

GUI Task Force

The GUI task force continues to work on a major revision of the E95 specification for Human Interfaces for Semiconductor Equipment. In addition to updating the specification with changes in software development, this revision will establish requirements for the usage of human interfaces on equipment using devices with small screens. The task force seems to be gaining consensus of many topics and getting ready to submit the ballot for voting.

Getting Involved

For those interested in participating, it is easy to join SEMI standards activities. Anyone can register at www.semi.org/standardsmembership.

All SEMI task force ballot activities are logged here.

After joining the standards activities, anyone can get involved. The task forces post everything on the connected @ SEMI website https://connect.semi.org/home. Here are the community names for the task forces covered in this blog:

• GEM 300 Task Force - North America
• Diagnostic Data Acquisition Task Force - North America
• Fab & Equipment Computer and Device Security (CDS) Task Force – North America
• Advanced Backend Factory Integration (ABFI) Task Force – North America
• Graphical User Interfaces (GUI) Task Force - North America

Background

Cimetrix CIMConnect^TM customers enjoy many benefits to maintaining an active support contract, and today we are announcing yet another one: access to a set of product-specific training videos.

A few years ago, the Solutions Engineering team at the Cimetrix Connectivity Group posted product training material including the full set of CIMConnect training PowerPoint presentations to facilitate self-training for those unable to attend a formal session. We update this repository periodically as the training material is revised and improved. The material is available online through the Customer Portal. After logging in, you can find the presentations here:

Training Videos

To complement the presentation material shown above, the Solutions Engineering team is now creating video training material. As of mid-June, 2021, the first set of training videos for CIMConnect is also available via the customer portal (see below).

By clicking on the “CIMConnect Video Library”, you can see full set of available training videos and access them via this table:

The material is organized by topic, such as Collection Events or Status Variables. Each topic is subdivided into one or more instruction parts. When there is a lab, the implementation of the lab is covered twice. First, the implementation of the lab is reviewed and demonstrated in CIMConnect’s “Getting Started” sample application. Second, the lab is implemented step by step from scratch in a new application.

A few of the training PowerPoint presentations are not yet complete but should be available soon. This includes topics like Remote Commands, Equipment Constants, Factory Setup, and Operator Interface. Solutions Engineering plans to expand the training to other products as well.

Also, note that other videos are also available that go beyond the scope of the training material. These are found on the same “CIMConnect Video Library” page at the bottom.

Customers are welcome to purchase CIMConnect training and/or consulting services at any time. The training material described above is not a substitute for working directly with a product and standards expert, where a customer can discuss specific equipment hardware, software architecture, and unique customer requirements. Nevertheless, this material should help our customers when they need a refresher course and especially when new employees are assigned to work with CIMConnect after its initial development.

For the first time since the Fall of 2019, the SEMI North America Information & Control Committee (I&CC) was finally able to meet and conduct business online. Throughout all of 2020, the I&CC was not able to meet because SEMI regulations did not at that time allow voting in online meetings. Instead, only the task forces have been meeting. As a result, any passing ballots, unless super clean, had to wait for adjudication in the North America I&CC.

This year, prior to the I&CC meeting on April 1 and 2, all of the associated task forces also met as usual, including the GEM 300, Diagnostic Data Acquisition (DDA), and Advanced Backend Factory Integration (ABFI) task forces. Moreover, the I&CC was able to conduct all the unresolved business that had accumulated over the last year. During the committee meeting, the I&CC successfully used the SEMI Virtual Meeting (SVM) software which runs in an internet browser, allows each committee member to log in, and allows for official voting to take place during the meeting. The North America I&CC will meet again during the summer.

GEM 300 Task Force

In the GEM 300 task force, the primary activity was to officially redefine its charter and scope to match what it has already been doing for the last 20 years. Each SEMI task force defines a “Task Force Organization Force” document (aka TFOF) to establish its charter and scope. Somehow, the GEM 300 task force charter and scope were severely out of date.

In addition to this update, some changes to the E5 standard finally passed voting, pending some final approval. The E5 changes include several new messages and establish definitions for commonly used data collection terminology. The new messages complement the existing set of messages by allowing the host to query information about the current data collection setup. Currently, it is common for a host program to reset and redefine all data collection after first connecting to an equipment because there has been no way to query this information. With these new messages, the host will be able to query the setup and confirm that no data collection has changed while disconnected. Finally, it will be easier to test GEM interfaces with these new messages.

The task force already approved tasks to consider some major work to the GEM standard. The task force is also considering changes to the E116 standard, but there is some resistance to these changes. Here is a summary table of the GEM-related standards activity from across the globe.

Region	Ballot	Standard(s)	Status	Topic
South Korea	5832	New	Cycle 5, 2020	Generic Counter
South Korea	6695	E87	Adjudication	Ready to unload prediction changes.
North America	6572	E30	Development	Add Stream 21, more stream 2, Cleanup Process Program Management.
North America	6552	E5	Adjudicated Spring 2021	Data collection setup, terminology. Ratification ballot proposed. 2 line-items pending since Summer 2020
North America	6598	E37, E37.1	Cycle 7, 2020	Standardize TCP/IP port numbers
North America	6597	E173	Adjudicated Spring 2021	Minor updates, clarification Pending since Spring 2020.
North America	6647	E116	SNARF Revision	Recommendations from the ABFI task force
North America	6683	E148	Development	Line item revision

 

DDA Task Force

In the Diagnostic Data Acquisition (DDA) task force (responsible for the EDA standards, aka Interface A), freeze 3 development is moving forward. All of the ballots still failed as expected. The number of remaining technical issues nevertheless has dwindled to just a handful. E132, E125, and especially E164 need the most work.

Following is a summary of the previously completed work.

And here is a summary of the work in progress.

 

All of the failed ballots will be reworked and resubmitted for voting. For many of these ballots, it will be the sixth time to go through the SEMI ballot procedure. Consensus is very nearly achieved, and the defects in the ballots have been identified and corrected. Additionally, there are plans to modify SEMI E179, the standard that defines how gRPC will be utilized. While testing EDA freeze 3, Cimetrix has identified two simple ways to modify the E179 protocol buffer files in order to reduce overhead. These and a few other changes will be proposed in a new ballot.

One of the last changes to the freeze 3 standards will be the introduction of passwords. In the current freeze 1 and freeze 2 versions, there are no passwords. Any client that knows a valid, unused Access Control List entry (ACL, the equivalent of a user name) can connect; therefore, there really isn’t any authentication unless using the SSL protocol with certificates. Passwords will enhance EDA security and facilitate EDA interface setup by allowing client applications to use the same ACL entry while defining a unique password to block other clients from using the same entry. The final E132 ballot will finalize the password feature.

The task force leaders are asking the voting members to raise any final issues before these ballots are submitted to SEMI to the next voting cycle so that we can approve these standards, give implementers a chance to experiment with EDA freeze 3, raise any serious issues that impede the implementation, and then propose the final changes which incorporate that feedback. Until a version of these standards is formally approved, it will be difficult to get concrete and widespread feedback on the new technology, which is a necessary precursor to its adoption and use.

ABFI Task Force

The Advanced Factory Integration task force passed more changes in E142 without controversy. The task force plans to create E142.4, another GEM implementation of E142, designed for larger wafer maps to allow for increased traceability possibilities. Additionally, the task force continues to make plans to develop an adoption matrix as a new standard to describe when GEM and GEM 300 standards should be adopted in backend equipment based on equipment features.

Background

The SEMI North America Diagnostic Data Acquisition (DDA) task force is part of the North America Information and Control Committee (I&CC or NA I&CC). This year the meeting that is normally held in conjunction with SEMICON West was held on Tuesday, July 14, 2020, and continued its activities in developing important SEMI standards. As co-leader of the NA DDA task force, I offer this blog as a summary of the current task force activities.

Freeze 3 Status

The primary responsibility of the DDA task force is the suite of Equipment Data Acquisition (EDA) standards, sometimes referred to as “Interface A.” Currently there are two version sets of EDA standards known as “Freeze 1” and “Freeze 2” which are both based on SOAP/XML over HTTP. The current activities are focused on defining the next EDA set (already designated “Freeze 3”) which is based on a binary protocol gRPC over HTTP. This technology, along with a number of other changes, promises to dramatically increase data collection throughput capacity.

Here is what has been completed so far:

Standard (Ballot)	Ballot Status	Lead
E132 (6337) – Client Authorization and Authentication	Published - 04/29/2019	Brian Rubow (Cimetrix)
E138 (6336) – Specification for XML Semiconductor Common Components	Published - 03/15/2019	Brian Rubow (Cimetrix)
E134 (6335) – Data Collection Management	Published – 03/29/2019	Inhyeok Paek (Link Genesis)
E120 (6434) – Common Equipment Model (CEM)	Published – 05/30/2019	Inna Skvortsova (SEMI)
E145 (6436) – Classification for Measurement Unit Symbols in XML	Published – 05/31/2019	Inna Skvortsova (SEMI)
E178 (6300) – Guide for EDA Freeze Version	Published – 01/10/2020	Mitch Sakamoto (ZAMA)
E179 (6344A) – Specification for Protocol Buffers Common Components	Published – 03/27/2020	Albert Fuchigami (PEER)

 

Current Ballot Activity

The bulk of the “Freeze 3” work is still under active development. Here is a summary of the ballot activity as of the start of the meeting on Tuesday.

Standard (Ballot)	Ballot Status	Lead
E125 (6527B) – Equipment Self Description (EqSD)	Adjudication	Brian Rubow (Cimetrix) Hyungsu Kim (Doople)
E132 (6571B) – Client Authorization and Authentication	Adjudication	Mitch Sakamoto (ZAMA) Albert Fuchigami (PEER)
E134 (6553B) – Data Collection Management	Adjudication	Brian Rubow (Cimetrix)
E164 – EDA Common Metadata	Development	Alan Weber (Cimetrix) Note – separate 5yr reapproval ballot started
E125.2 (6345) – gRPC Binding for Equipment Self Description (EqSD)	Development	Albert Fuchigami (PEER)
E132.2 (6346C) – gRPC Binding for Client Authorization and Authentication	Adjudication	Albert Fuchigami (PEER)
E134.2 (6347) – gRPC Binding for Data Collection Management	Development	Albert Fuchigami (PEER)

 

All of the ballots failed and will be reworked for Cycle 7 voting later this year. However, this was not unexpected, and a great of useful feedback was gathered in the process.

Getting Involved

For those interested in participating, it is easy to join SEMI standards activities. Anyone can register at www.semi.org/standardsmembership.

All SEMI task force ballot activities are logged at: http://downloads.semi.org/web/wstdsbal.nsf/TFOFandSNARFsbyCommittee?OpenView&Start=1&Count=1000&ExpandView

After joining the standards activities, anyone can get involved. The task forces post everything on the connected @ SEMI website https://connect.semi.org/home. The North America DDA task force community is called “Diagnostic Data Acquisition Task Force - North America”.

To find out more about the semi standards, or to speak with a standards expert, click the button below: