Industry News, Trends and Technology, and Standards Updates

Brian Rubow: Director of Solutions Engineering

Brian Rubow is the Director of Solutions Engineering for Cimetrix. He is well-known within the industry due to his involvement with the SEMI standards committees. He currently serves as the co-chairs for the North America Information and Control Committee, the North America GEM300 Task Force, and the North America DDA Task Force. Rubow has both a bachelor’s and a master’s in Engineering from Brigham Young University.
Find me on:

Recent Posts

North America Information & Control Committee Fall 2023 Update

Posted by Brian Rubow: Director of Solutions Engineering on Nov 30, 2023 12:32:00 PM

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. 

SEMI-Fall-2023-pic1

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. 

SEMI-Fall-2023-pic2

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.

SEMI-Fall-2023-pic3

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.

Contact Us

Topics: Industry Highlights, SECS/GEM, Semiconductor Industry, Smart Manufacturing/Industry 4.0, Cimetrix Products, Standards

North America Information & Control Committee Summer 2023 Update

Posted by Brian Rubow: Director of Solutions Engineering on Aug 9, 2023 10:15:00 AM

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.

Topics: Industry Highlights, SECS/GEM, Semiconductor Industry, Smart Manufacturing/Industry 4.0, Cimetrix Products, Standards

North America Information & Control Committee Spring 2023 Update

Posted by Brian Rubow: Director of Solutions Engineering on Apr 11, 2023 9:45:00 AM

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. 

Topics: Industry Highlights, SECS/GEM, Semiconductor Industry, Doing Business with Cimetrix, Smart Manufacturing/Industry 4.0, Standards

GEM Standard Update October 2022

Posted by Brian Rubow: Director of Solutions Engineering on Oct 31, 2022 10:45:00 AM

Background

Chris Maloney of Intel and I are the North American GEM 300 Task Force co-leaders. We lead the task force activity related to all SEMI standards related to GEM technology. This includes a long list of SEMI standards.

APCSM Conference

I recently participated in the APCSM (Advanced Process Control Smart Manufacturing) conference in Austin, Texas by teaching about the GEM standard. In the material I presented, I included what I called the “core philosophies of GEM”. These are the features in GEM that justify the increased adoption and usage of GEM technology. These core philosophies include:


Two Levels of Subscription

An equipment’s GEM interface serves as a message broker and much more. It is not just a simple on/off message subscription service. The end user host has substantial control to dictate the content of each message coming from the equipment. The same GEM interface might send fewer and smaller messages at one end user site and send many and larger messages at another, based on the data collection setup by each’s end user’s host. Compare the following features to a typical message broker subscription model, where a client can only subscribe to receive or not receive specific messages but has no control over the message content or frequency.

Collection event reports allow the end user to enable and disable collection event message notifications, a typical client subscription model. As a second level of subscription, the end user also can choose the data reported in those messages.

Trace reports allow the end user to choose the trace report message frequency. As a second level of subscription, the end user also chooses the data reported in those messages.

GEM-update-Oct-2022-pic1

Alarm reports allow the end user to enable and disable alarm message notifications. As a second level of subscription, the end user also independently chooses the collection event report configuration for the collection events associated with the alarms.

Adaptability

Any manufacturing equipment, simple or complex, can have a GEM interface. The GEM interface complexity reflects the equipment’s complexity. For example, one GEM interface might have 15 unique collection events yet another might have 20,000. One equipment might have 10 status variables while another has over 5,000.

Additionally, the technology within a GEM interface is mature enough that it is possible to implement a GEM interface on equipment platform, be that Windows, Linux, a PLC or any other operating system. A surprising number of equipment are still using older software development technology including Visual Basic 6.0 and Visual C++ 6.0, but these can still implement GEM. And yes, even an equipment implemented completely on a PLC could have a minimalistic GEM interface within the PLC using serial communication or TCP/IP. The GEM standard allows implementation to choose to implement capabilities or not based on what is appropriate.

Extensibility

It is easy to add additional collection events, alarms and variables to an existing GEM interface without affecting backward compatibility. And once new items are in the GEM interface, the end user host can use the data or not as desired.

It is also to combine requirements from different sources and put them together in one GEM interface. To explain further, requirements for a GEM interface will come from different end users, the GEM standard itself, the equipment supplier and from additional standards. It is relatively into to combine the requirements from all of these sources into one GEM interface. And the combined data collection features can be combined together inherently is trace reports and collection event reports.

GEM-update-Oct-2022-pic2

Top-Down Connectivity

In many situations it can be useful to give one equipment access to data from another equipment. One possible solution for this is direct equipment-to-equipment communication. However, when using GEM while direct equipment-to-equipment connectivity is not prohibited, it is not normally used. Instead, GEM uses a top-down approach to connectivity. This means that the end user host collects information from one equipment using its GEM interface, and then the end user host passes that information to the downstream equipment. While this might seem less efficient because it is indirect, this top-down approach can be easier to integrate on the factory floor. Reasons include:

1. The scenarios can be equipment agnostic. Validating equipment-to-equipment communication can be difficult. And you can’t easily swap one equipment from one supplier with equipment from other. Each equipment only has be tested with one host entity.

2. This is easier for the equipment supplier to support. The equipment supplier only must support the GEM interface, not an additional equipment-to-equipment protocol.

3. This gives mores control to the end user. The end can log precisely what is occurring with each equipment, and can even manipulate the information if necessary. And independent connection between equipment is an additional complication when diagnosing issues.

GEM-update-Oct-2022-pic4

Exciting Changes to the GEM Standard

In a couple weeks ballot 6572C, a proposal to modify the SEMI E30 GEM standard, will be adjudicated during the Fall North American Information & Control Committee. The meeting will be held on November 9, 2022 at SEMI headquarters in Milpitas, CA. This ballot proposes the biggest changes to the GEM standard in many years. Since this is the fourth round of balloting these changes, it seems highly likely that the changes will be approved, especially since the voting in the last round indicated strong support for the changes. Following is a summary of the proposed changes

Process Program Management

Several changes are proposed related to the handling of equipment recipes, a.k.a. process programs. The biggest change is a proposal to officially adopt the Stream 21 SECS-II messages previously approved in the SEMI E5 (SECS-II) standard, which is the library for all standard message definitions. Stream 21 messages will allow equipment to transfer unformatted process programs to and from the equipment even when they are greater than 16.7 MB. This is a long overdue enhancement to the GEM standard, which current defines alternative ways to support large process programs which are complicated enough that few if any have ever implemented it.

Additionally, the process program management section has been completely reorganized to isolate each implementation alternative, so make it easier to identify the set of scenarios. For example, here is a new table summarizing the messages for each scenario:

Table 7 SECS-II Message Summary For Each Process Program Management Option

GEM-update-Oct-2022-graph

Each process program implementation alternative removed from the main body of the GEM standard has been relocated into an appendix.

The hope is that recipe management will be easier to understand, easier to implement, and able to handle the increasing size of process programs will less effort.

Additional New Messages

Ballot 6572C also proposes the addition of new message S2F51 through F64. These messages were also previously approved in the SEMI E5 (SECS-II) standard and are now proposed to be added to the GEM standard. These message add additional transparency to a GEM interface. Here is a quick summary of the new messages:

Message Description
S2F51 A request to the equipment to return the list of all report identifiers.

S2F53

A request to return one or more report definitions
S2F55 A request to the equipment to return the list of linked reports identifiers for one or more collection events.
S2F57 A request to the equipment to return the list of all collection event identifiers that are enabled for reporting.
S2F59 A request to the equipment to return the list of streams and functions that are to be spooled whenever spooling is active.
S2F61 A request to the equipment to return the list of all trace identifiers.
S2F63 A request to the equipment to return the list of one or more trace definitions.

 

These new messages not only make a GEM interfaces setup and configuration more transparent, but they also will allow for improved GEM interface testing. For example, it will be possible to test a GEM interface following steps like these:

1. Define a report using message S2F33
2. Check the report existence using new message S2F51
3. Check the report definition using new message S2F53
4. Link the report to a collection event using message S2F35
5. Check the report linking using new message S2F55
6. Enable the collection event using message S2F37
7. Check for the collection event enable status using new message S2F57
8. Disconnect from the equipment and restart the equipment
9. Check the report existence using new message S2F51
10. Check the report definition using new message S2F53
11. Check the report linking using new message S2F55
12. Check for the collection event enable status using new message S2F57

Today it is common for a host when it reconnects to a GEM interface to redefine the data collection, to ensure that the data collection was not changed while it was not connected where another host application might have modified the data collection setup. Instead of redefining the data collection, a host can verify whether the data collection is still the same.

Equipment Identification

Today an equipment is identified through a GEM interface using the equipment’s software revision and model number. Two equipment of the same model number and running the software revision cannot be easily distinguished.

A few new identification features were added.

E30EquipmentSupplier This is a new proposal to identify the equipment supplier.
EqpSerialNum The equipment’s serial number. This has been part of the E5 SECS-II standard for many years, but was not required by the GEM standard.
EqpName A name assignable by the operator or host. This has been part of the E5 SECS-II standard for many years, but was not required by the GEM standard

 

Improved equipment identification should assist Advanced Process Control applications.

Documentation Access

One of the common difficulties using a GEM interface is getting access to the correct documentation for an equipment, and the right version of that documentation. This ballot proposes providing two ways to obtain GEM documentation through a GEM interface.

1. Download the traditional GEM documentation, which might be a PDF or CSV file.
2. Download the SEDD file, an XML file describing the GEM interface. SEDD stands for SECS Equipment Data Dictionary.

In both cases, the documentation is downloaded using Stream 21 messages, the same new message available for process program transfer.

Miscellaneous Changes

There are a handful of other changes also proposed. SEMI somewhat recently adopted requirements for restricted bias terminology and guidelines for other biased terminology. Although no restricted bias terms were in the GEM standard, some biased terms are present. The ballot address bias terms that can be addressed following SEMI guidelines.

The GEM compliance statement has also been updated to reflect changes to GEM. The new compliance statement looks like this:

GEM-update-Oct-2022-table

 

Topics: Industry Highlights, SECS/GEM, Semiconductor Industry, Doing Business with Cimetrix, Smart Manufacturing/Industry 4.0

EDA Freeze 3 Update September 2022

Posted by Brian Rubow: Director of Solutions Engineering on Sep 29, 2022 10:45:00 AM

Background

As one of the North American DDA Task Force co-leaders, I am often asked when EDA Freeze 3 will be ready to implement. The SEMI DDA Task Force has been working on developing an EDA Freeze 3 standard for several years. This is an updated version of the data collection standard for manufacturing equipment. Unfortunately, due to many factors, this work has been slow to develop. For more information on a “freeze version” see SEMI standard E178 where official freeze versions are defined.

Status

To date the following ballots have been completed:

Standard (Ballot)

Ballot Status

E138 (6336) Published - 03/15/2019
E120 (6434) Published – 05/30/2019
E145 (6436) Published – 05/31/2019
E178 (6300) Published – 01/10/2020
E179 (6803) Published – 03/11/2022
E132 (6719A) Published – 04/29/2022
E132.2 (6346F) Published – 04/29/2022
E125 (6718A) Published – 04/22/2022
E134 (6720A) Final publication approval. Possibly 09/2022 but certainly by 10/2022.
E134.2 (6347A) Final publication approval. Possibly 09/2022 but certainly by 10/2022.
E179 (6837) Approved - In Publication Queue
E125.2 (6345A) Final publication approval. Possibly 09/2022 but certainly by 10/2022.
E125 (6891) Final publication approval. Possibly 09/2022 but certainly by 10/2022.
E179 (6892) Approved - In Publication Queue
E120.2 (6908) Final publication approval. Possibly 09/2022 but certainly by 10/2022.

 

In the last summer 2022 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. Since then SEMI has been working very hard to catch up standard publication.

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.

Current Ballots

There are two ballots currently open for voting. Adjudication on the voting will occur during North America SEMI Fall meetings the second week of November at SEMI headquarters (attendees can also attend remotely).

Ballot 6947

Ballot 6997 is an update to SEMI E179, a foundation standard for EDA freeze 3 defining how gRPC is applied to the standards and other important definitions. This ballot has three line items.

1. Fix a defect in the definition of Arrays discovered by the Cimetrix Software Engineering team.
2. Clarification of the usage of the “one of” keyword
3. Address changes related to conformance to the SEMI style manual.

Ballot 6946

This ballot includes 5 line items, including work from a few contributors.

1. Clarify some definitions and concepts.
2. A complete rework of ACL passwords and security scenarios.
3. Rework EstablishSession and ChangeSessionEndpoint functionality.
4. Fix some issues discovered during the vender test session #1.
5. Clean up some spelling errors and the usage of .proto files.

The rework of ACL passwords and security was submitted by Cimetrix. In current EDA freeze 1 and freeze 2, there are no passwords where authentication only occurs when SSL is used. Passwords were introduced to E132 in a previous ballot, passed voting and were published. The intention is provide some security despite not using SSL. However, a security review of the current password implementation revealed some issues with the authentication. The ballot proposes the introduction of a challenge token which allows an EDA client to prove knowledge of the correct password, as outlined in this scenario:

Client Session

Direction

Equipment Server

Client Session is assumed to know the equipmentId, clientId and plaintext ACL password. The equipmentId can be obtained using the InterfaceDiscovery interface.

 

 

GetEquipmentInformationRequest
(equipmentId, clientId)

 

 

 

Generate a challengeToken value associated with the equipmentId and clientId.

 

← 

GetEquipmentInformationResponse
(aclEntrySalt, challengeToken)

Client Session uses aclEntrySalt and plaintext ACL password to generate the passwordHash.

 

 

Client Session uses the challengeToken and passwordHash to generate a client challengePasswordHash

 

 

Equipment Server uses the challengeToken and passwordHash to generate its version of challengePasswordHash

 

EstablishSessionRequest (equipmentId, clientId, challengePasswordHash)

 

Client Session provided challengePasswordHash equals Equipment Server’s version challengePasswordHash

Generate the sessionId.

 

EstablishSessionResponse
(sessionID)

 

At no point is an EDA client required to include the password or hashed password when establishing a session. To keep passwords secure, administrative EDA clients should use SSL when adding ACL entries. This increase in security is expected to allow for the adoption of EDA standards in a wider spectrum of applications.

Known Future Ballots

  • An update to E164.
  • Another update to E132, E125, and E134. A proposal was made to redefine the terms “client” and “consumer”. This week, the task force decided to go forward with this proposal.
    • The adoption of gRPC allows EDA clients to receive NewData messages with a bi-directional (full duplex) connection. In EDA freeze 1 and 2, SOAP message over HTTP are only one-directional. This new bi-directional use case muddied the meaning of “client” and “consumer”. The proposal will clarify how a “client” is the entity that initiates communication with the “equipment server”. When configured to do so, an “equipment server” can initiate communication with a “consumer”. So there may or may not be a consumer present.
    • EDA Freeze 3 also introduces three classifications of messages from the equipment server, heartbeat, operational, and notification messages. The heartbeat and operational are sent either to the client (in bi-directional mode), to the consumer or are disabled entirely. Notification messages can be sent to client and/or consumer.
  • The task force plans to organize another test session open to anyone interested, where E132, E120, E125 and E134 can all be tested together. This had been planned for early 2023, but dates have not been proposed and these plans may slip. This test is expected to validate whether the published standards are ready. The task force leaders expect that some issues might be revealed and further changes to E125 and E134 may be required. If so, EDA freeze 3 might not be ready until spring 2024.
  • An update to E178 Guide for EDA Freeze Version. This is the final step to officially declare the freeze 3 version.

To summarize, while the EDA Freeze 3 is not getting completed as quickly as most would like, the work is progressing. There aren’t any major hurdles at this time, but it lots of time and effort to complete the work that has already been planned.

 

Topics: Industry Highlights, Semiconductor Industry, EDA/Interface A, Doing Business with Cimetrix, Smart Manufacturing/Industry 4.0

Summer 2022 North America Information & Control Committee Report

Posted by Brian Rubow: Director of Solutions Engineering on Jul 26, 2022 10:00:00 AM

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.

Region

Ballot

Standard(s)

Status

Topic

Korea

5832

New

?

Generic Counter

NA

6572

E30

Adjudication

Add Stream 21, more stream 2, Cleanup Process Program Management.

NA

6835

E87

Development

Carrier Ready to Unload Prediction update

NA

6836

E87/E90

Development

Extending substrate characteristics, such as for Bonder/Debonder support and other applications

NA

6859

E116

Adjudication

Recommendations from the ABFI task force

NA

6893

E5

Published

Errata

China

6914

E87

Development

Modify E87 to allow for more equipment adoption, particularly in the semiconductor backend.

NA

6916

E5

Adjudication

FormatCode for OperatorCommand. Various Errata.

 

 

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:

Standard (Ballot)

Ballot Status

E138 (6336)

Published - 03/15/2019

E120 (6434)

Published – 05/30/2019

E145 (6436)

Published – 05/31/2019

E178 (6300)

Published – 01/10/2020

E179 (6803)

Published – 03/11/2022

E132 (6719A)

Published – 04/29/2022

E132.2 (6346F)

Published – 04/29/2022

E125 (6718A)

Published – 04/22/2022

E134 (6720A)

Approved - In Publication Queue

E134.2 (6347A)

Approved - In Publication Queue

E179 (6837)

Approved - In Publication Queue

E125.2 (6345A)

Approved - In Publication Queue

E125 (6891)

Approved - In Publication Queue

E179 (6892)

Approved - In Publication Queue

E120.2 (6908)

Approved - In Publication Queue

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

Topics: Industry Highlights, SECS/GEM, Semiconductor Industry, EDA/Interface A, Doing Business with Cimetrix, Smart Manufacturing/Industry 4.0, Standards

A New Benefit for our CIMConnect Customers: Training Videos Available Now

Posted by Brian Rubow: Director of Solutions Engineering on Nov 24, 2021 11:45:00 AM

Background

Cimetrix CIMConnectTM 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:

CIMConnect-training-videos-pic1

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).

CIMConnect-training-videos-pic2

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

CIMConnect-training-videos-pic3

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.

Topics: Industry Highlights, SECS/GEM, Semiconductor Industry, Smart Manufacturing/Industry 4.0, Cimetrix Products

Standards Activity Report SEMI NA Spring 2021

Posted by Brian Rubow: Director of Solutions Engineering on May 12, 2021 11:45:00 AM

Stcked_Standards_logoFor 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.

Standard (Ballot)

Ballot Status

Lead

E132 (6337)

Published - 04/29/2019

Brian Rubow (Cimetrix)

E138 (6336)

Published - 03/15/2019

Brian Rubow (Cimetrix)

E134 (6335)

Published – 03/29/2019

Inhyeok Paek (Link Genesis)

E120 (6434)

Published – 05/30/2019

Inna Skvortsova (SEMI)

E145 (6436)

Published – 05/31/2019

Inna Skvortsova (SEMI)

E178 (6300)

Published – 01/10/2020

Mitch Sakamoto (ZAMA)

E179 (6344A)

Published – 03/27/2020

Albert Fuchigami (PEER)


And here is a summary of the work in progress.

Standard (Ballot)

Ballot Status

Lead

E125 (6718)

Development

Brian Rubow (Cimetrix)

Hyungsu Kim (Doople)

E132 (6719)

Development

Mitch Sakamoto (ZAMA)
Albert Fuchigami (PEER)

E134 (6720)

Development

Brian Rubow (Cimetrix)

E164

 

Alan Weber (Cimetrix)

E125.2 (6345)

Development

Albert Fuchigami (PEER)

E132.2 (6346E)

Development

Albert Fuchigami (PEER)

E134.2 (6347)

Development

Albert Fuchigami (PEER)

E125 (6527C)

To Abolish

Replaced by 6718

E132 (6571C)

To Abolish

Replaced by 6719

E134 (6553C)

To Abolish

Replaced by 6720

 

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.

Topics: Industry Highlights, SECS/GEM, Semiconductor Industry, EDA/Interface A, Doing Business with Cimetrix, Smart Manufacturing/Industry 4.0, GEM300, Standards

Summer 2020 North America DDA Task Force Report

Posted by Brian Rubow: Director of Solutions Engineering on Aug 12, 2020 10:45:00 AM

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:

Ask an Expert

Topics: Industry Highlights, Semiconductor Industry

Summer 2020 North America ABFI Task Force Report

Posted by Brian Rubow: Director of Solutions Engineering on Aug 5, 2020 11:00:00 AM

Background

The SEMI North America Advanced Backend Factory Integration (ABFI) task force is part of the North America Information and Control Committee (I&CC or NA I&CC). Normally this task force meets every July in San Francisco as part of SEMICON West. However, this year the technical committee meetings are spread out over several weeks and do not coincide directly with the exhibition. Additionally, the I&CC did not meet at all because SEMI regulations do not currently allow TC Chapter (Committee) voting in virtual meetings. That will hopefully change later this year, but for now delays SEMI standards development.

Regardless of these challenges, the ABFI task force did meet on Monday July 13, 2020 and continues to develop SEMI standards. I am co-leader of the NA ABFI task force along with Dave Huntley of PDF Solutions. This blog is a summary of the current task force activities.

Wafer Maps

Ballot 6648 to update to the SEMI E142 (Specification for Substrate Mapping) specification has passed initial voting and is recommended to be accepted and published. This ballot significantly enhances the amount of traceability data that may be embedded within wafer maps.

Additional Wafer Map Activity

Because wafer maps will potentially be much larger with additional traceability data, they could be too large for the messages currently defined in the E142.2 standard. A new activity has been started to modify wafer map usage further and to allow Stream 21 messages to be used for wafer map transfer. The stream 21 message in the SECS-II standard can be used to transfer very large items through a GEM interface.

SEMI Standard Usage Matrix for Backend

The ABFI task force is also defining a matrix that specifies which standards beyond GEM (E30), SECS-II (E5), HSMS (E37) and Substrate Mapping (E142) should be used for backend automation, and under what conditions they should be used. This includes consideration of the full suite of GEM 300 standards and other standards that all GEM interfaces should consider, such as SEDD (E172) and SMN (E173).

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 ABFI task force does not have a community.

To learn more about the standards, or to speak with a standards expert, click on the button below:

Ask an Expert

Topics: Industry Highlights, Semiconductor Industry, Standards