INCREMENTAL IMPLEMENTATION STEPS NOTICE: This Related Information is not an official part of SEMI E170 and was derived from the work of the global Information and Control Technical Committee. This Related Information was approved for publication by full letter ballot procedures on [A&R approval date]. Purpose of Incremental Implementation Steps To make implementation barrier lower, following Introduction of Incremental Implementation Steps — deployment steps are considered and recommended. Step 3A and Step 3B are independent and can be implemented in either order. Step 4 is the completion of E170 implementation with both 3A and 3B implemented. Incremental Implementation Steps Steps Step 1 Step 2 Step 3A1 Step 3A2 Step 3B Step 4 Introduced E170 Message Set with SRS Management PRC Space PRC Operation RAC Operation All Capability RecipeXID Purpose Introduce Completion of Introduce E170 Introduce E170 Introduce recipe Introduce cache Remote Access E170 recipe transaction Secured Recipe space switching operation for function for implementation capability Space function for production recipe SPORM (Preparation of management production transaction Extended Recipe capability execution efficiency ID capability) Precondition None Step 1 Step 2 Step 3A1 Step 2 Step 3A or 3B (Decision to go (PEMFlag is not with E170) needed) E170 Messages SRS Object Implementation PRC Space PRC Object RAC Space All components for Recipe except PEMFlag PEMFlag RAC Object Upload and Download Expected Effects Multiple recipe Secured Recipe PRC Space is Efficient Remote Access Full effect of upload or Spaces are usable usable for secure transaction of of recipes on E170 download by production recipe recipe by cache Recipe Server by Optional Recipe single message is handling operation using supplier Spaces can be supported provided recipe assigned to (Pre-Download (Cache Mode, applications on (Conventional differently Mode, Full Full Query equipment or messaging are privileged Download Mode) Mode) workstation not affected and operator groups are also usable) Available Extended recipe SRS PEMFlag which PRC operations RAC operations All E170 Operations and identification by Management selects recipe functionalities Functions RecipeXID (Security Class space for E40 PJ for SPORM management by Multiple recipes SecurityID) by single message
INCREMENTAL IMPLEMENTATION STEPS NOTICE: This Related Information is not an official part of SEMI E170 and was derived from the work of the global Information and Control Technical Committee. This Related Information was approved for publication by full letter ballot procedures on [A&R approval date]. Purpose of Incremental Implementation Steps Introduction of Incremental Implementation Steps — To make implementation barrier lower, following deployment steps are considered and recommended. Step 3A and Step 3B are independent and can be implemented in either order. Step 4 is the completion of E170 implementation with both 3A and 3B implemented. Incremental Implementation Steps Steps Step 1 Step 2 Step 3A1 Step 3A2 Step 3B Step 4 Introduced E170 Capability Message Set with RecipeXID SRS Management PRC Space PRC Operation RAC Operation All Purpose Introduce E170 recipe transaction capability (Preparation of Extended Recipe ID capability) Introduce E170 Secured Recipe Space management capability Introduce recipe space switching function for production execution Introduce cache operation for production recipe transaction efficiency Introduce Remote Access function for SPORM Completion of E170 implementation Precondition None (Decision to go with E170) Step 1 Step 2 Step 3A1 Step 2 (PEMFlag is not needed) Step 3A or 3B Implementation E170 Messages for Recipe Upload and Download SRS Object except PEMFlag PRC Space PEMFlag PRC Object RAC Space RAC Object All components Expected Effects Multiple recipe upload or download by single message is supported (Conventional messaging are not affected and are also usable) Secured Recipe Spaces are usable Optional Recipe Spaces can be assigned to differently privileged operator groups PRC Space is usable for secure production recipe handling (Pre-Download Mode, Full Download Mode) Efficient transaction of recipe by cache operation (Cache Mode, Full Query Mode) Remote Access of recipes on Recipe Server by using supplier provided recipe applications on equipment or workstation Full effect of E170 Available Operations and Functions Extended recipe identification by RecipeXID Multiple recipes by single message SRS Management (Security Class management by SecurityID) PEMFlag which selects recipe space for E40 PJ PRC operations RAC operations All E170 functionalities for SPORM
5888.docx