downloads.semi.orgdownloads.semi.org/.../$file/5735.docx · web viewthe definition of this notation...

Background Statement for SEMI Draft Document 5735Line-item Revision to SEMI E171-0914 Specification for Predictive Carrier Logistics

Note: This background statement is not part of the balloted item. It is provided solely to assist the recipient in reaching an informed decision based on the rationale of the activity that preceded the creation of this document.

Note: Recipients of this document are invited to submit, with their comments, notification of any relevant patented technology or copyrighted items of which they are aware and to provide supporting documentation. In this context, “patented technology” is defined as technology for which a patent has issued or has been applied for. In the latter case, only publicly available information on the contents of the patent application is to be provided.

Background

Through the adjudication of the document #5486A PCL and the feedbacks after the first publication as SEMI E171-0914 PCL, following revisions are proposed and agreed.Note that, for simplicity, the section numbers in the quotation of E171-0914 in this ballot are used for explanations unless otherwise noted.

1. Line-item #1: Elimination of PEC while preserving Carrier Flow management capability Motivation

As an action item from the adjudication process of Document #5486A PCL, a new business which removes the optional PEC concept is proposed and agreed to simplify the document. Thought equipment may need to handle multiple carrier flows depending on its operational capability, definition such as PEC, which explains the operation in inside of equipment, is not needed.

Action

Delete Optional PEC Concept Preserve the capability to deal with multiple carrier flows, keep functionality of PECID by renaming it as

CarrierFlowID for optional use.

Impact

These changes have no impact to implementation.

2. Line-item #2: Improvement of convention on optional expressions and state report clarifications

Motivation

The definition of Reqd column in convention, which is quoted from E87, is not sufficient because it does not have definition of mnemonics for option and condition.

As a result, Reqd column of Table 21 is not appropriately used. Example in Table 1 is not needed.

Action

Define mnemonics for required, optional, and conditional. Delete example in Table 1. Correct Reqd column of Table 21 according to the Definition column.

Impact

1

These changes have no impact to implementation.

3. Line-item #3: Add explanations to Appendix Motivation

Explanations in appendix are not enough.

Action

Add more explanations to appendix

Impact

No specification change

4. Line-item #4: Rename prediction related mnemonics and add explanations as needed Motivation

The use of same or similar mnemonics for the explanations both actual states and predictions made confusions. Also, explanations of the prediction by equipment are not sufficient.

Action

Rename prediction related mnemonics. Add more explanations on predictions

Impact

Clarifications are done.

5. Line Item #5: Improve / correct wordings and add explanations as needed Motivation

There are some expressions needed to be improved or corrected from wording view point. There are some parts more explanations are expected.

Action

Improve wordings and add explanations as needed.] Note that this line item is not numbered by <#5> and </#5>, underlines are used for addition and double

strikeouts are used for deletion.

Impact

No impact to any specifications.

6. Line-item #6: Add internal buffer scenarios Motivation

Scenarios for internal buffer equipment are not included in current revision.

Action

Add internal buffer scenarios to appendix.

Impact

No impact to any specifications.

Note in the proposals, line items are distinguished by colors. The start point of a line item is marked with the line item number as <#n>, and the end point of a line item is marked with the line item number as </#n>. The added text

2

is typically highlighted with underline. Removed text is typically denoted with double strikeout marks (on the bottom for figure). Deleted figure is denoted with <#n>Delete</#n>, added figure is denoted with <#n>Add</#n> (may be nested in the tags with the same number). These markings are for highlight in the ballot only. They are not proposed to be included in the updated standard. Where the proposals show text extracted from the existing standard, any references in the text are aligned with current section numbering. However, recognize that various proposals may add or remove sections, requiring adjustment of references. This ballot assumes that SEMI will adjust these references prior to publication.

3

Revision Control

This revision control records activity within the task force as well as formal submit and resubmit dates and results per SEMI. Entries have been made by the task force.

Date Version Name Edits

Oct. 15, 2014 1.0 Terry Asakawa The first line item ballot

Review and Adjudication InformationTask Force Review Committee Adjudication

Group: Japan PCL TF Japan TC Chapter of Global Information & Control Technical Committee

Date: Thursday, December 4, 2014 Friday, December 5, 2014Time & Time Zone: 10:00-13:30 [JST] 11:00-17:00 [JST]Location: Tokyo Big Sight Conference Tower Tokyo Big Sight Conference TowerCity, State/Country: Tokyo, Japan Tokyo, JapanLeader(s): Terry Asakawa (Tokyo Electron Limited)

Yuko Toyoshima (Hitachi High-Technologies)

Takayuki Nishimura (SCREEN Semiconductor Solutions Co., Ltd)Mitsuhiro Matsuda (Hitachi Kokusai Electric Inc.)

Standards Staff: Chie Yanagisawa (SEMI Japan)81.3.3222.5863 / cyanagisawa @semi.org

Chie Yanagisawa (SEMI Japan)81.3.3222.5863 / cyanagisawa @semi.org

Task Force Review meeting’s details are subject to change, and additional review sessions may be scheduled if necessary. Contact the task force leaders or Standards staff for confirmation.

Telephone and web information will be distributed to interested parties as the meeting date approaches. If you will not be able to attend these meetings in person but would like to participate by telephone/web, please contact Standards staff.

This line-item ballot includes the purpose, scope, limitations and terminology sections per SEMI Standards Procedure Guide.

If you need a copy of the documents in order to cast a vote, please contact the following person within SEMI. Chie YanagisawaSEMI Standards, SEMI JapanTel: 81.3.3222.5863Email: [email protected]

Please be advised that voter requests for access to the full Standard must be made at least three business days before the voting deadline. Late requests may not be honored, and if the Standard is not available for this reason, the voter may not use this as justification for rejecting the ballot.

4

mailto:[email protected]

mailto:[email protected]

DRAFTDocument Number: 5735

Date: 5/7/23

SEMI Draft Document 5735Line-item Revision to SEMI E171-0914: SPECIFICATION FOR PREDICTIVE CARRIER LOGISTICS (PCL)

Make following line item revisions to the specified part of E171-0914.Note that, for simplicity, the section numbers in the quotation of E171-0914 in this ballot are used for explanations unless otherwise noted.

Line Item #1: Elimination of PEC while preserving Carrier Flow management capability

Line Item #2: Improvement of convention on optional expressions and state report clarifications

Line Item #3: Add explanations to Appendix

Line Item #4: Rename prediction related mnemonics and add explanations as needed

#4-1 Rename following mnemonics as shown below, as editorial changes. These editorial changes are not shown by <#4> and </#4> in quoted part of this document to avoid to be busy and are applied to the entire document including the part revised by other line item revisions passed.

From To Note (Not used for revision)

SoLR Prediction LR Prediction Load Request PredictionEoLR Prediction LS Prediction Load Stagnation PredictionSoUR Prediction UR Prediction Unload Request PredictionEoUR Prediction US Prediction Unload Stagnation Prediction

SoLR Predictable LR Predictable Load Request PredictableEoLR Predictable LS Predictable Load Stagnation PredictableSoUR Predictable UR Predictable Unload Request PredictableEoUR Predictable US Predictable Unload Stagnation Predictable

SoLR Event LRP Event Load Request Prediction EventEoLR Event LSP Event Load Stagnation Prediction EventSoUR Event URP Event Unload Request Prediction EventEoUR Event USP Event Unload Stagnation Prediction Event

SoLRPState LRPState Load Request Prediction StateEoLRPState LSPState Load Stagnation Prediction StateSoURPState URPState Unload Request Prediction StateEoURPState USPState Unload Stagnation Prediction State

SoLRPTime LRPTime Load Request Predicted TimeEoLRPTime LSPTime Load Stagnation Predicted TimeSoURPTime URPTime Unload Request Predicted TimeEoURPTime USPTime Unload Stagnation Predicted Time

SoLR Not Predicted LR Not Predicted Load Request Not PredictedSoLR Predicted LR Predicted Load Request PredictedEoLR Not Predicted LS Not Predicted Load Stagnation Not PredictedEoLR Predicted LS Predicted Load Stagnation PredictedSoUR Not Predicted UR Not Predicted Unload Request Not PredictedSoUR Predicted UR Predicted Unload Request PredictedEoUR Not Predicted US Not Predicted Unload Stagnation Not Predicted

This is a Draft Document of the SEMI International Standards program. No material on this page is to be construed as an official or adopted Standard or Safety Guideline. Permission is granted to reproduce and/or distribute this document, in whole or in part, only within the scope of SEMI International Standards committee (document development) activity. All other reproduction and/or distribution without the prior written consent of SEMI is prohibited.

Doc. 5735 SEMI

Semiconductor Equipment and Materials International3081 Zanker RoadSan Jose, CA 95134-2127Phone: 408.943.6900, Fax: 408.943.7943


Date: 5/7/23

EoUR Predicted US Predicted Unload Stagnation Predicted

SoLRNotPredicted LRNotPredicted Load Request Not PredictedSoLRPredicted LRPredicted Load Request PredictedEoLRNotPredicted LSNotPredicted Load Stagnation Not PredictedEoLRPredicted LSPredicted Load Stagnation PredictedSoURNotPredicted URNotPredicted Unload Request Not PredictedSoURPredicted URPredicted Unload Request PredictedEoURNotPredicted USNotPredicted Unload Stagnation Not PredictedEoURPredicted USPredicted Unload Stagnation Predicted

#4-2 Improve figures and add explanations to section 7 Conceptual Descriptions.

#4-3 For simplification, delete entire section 7.10 as the section is redundant because cascading issue is covered by section 7.5.2. Instead, add Figure 5 ‘Definition of CEW in Three Load Port Fixed Buffer Equipment’ to section 7.5.2 in order to show multiple load port case as three load port case is simpler but easily implies four load port case.

#4-4 Add explanations to section 10.3.2 Predictions

#4-5 Make related revisions marked with <#4> and </#4>

Line Item #5: Improve / correct wordings and add explanations as needed

#5-1 Replace all “Simple Fixed Buffer Equipment” in Appendix 1 with “Typical Fixed Buffer Equipment” (not shown in the quoted part to avoid complexity).

Line Item #6: Add internal buffer scenarios

Note in the proposals, line items are distinguished by colors. The start point of a line item is marked with the line item number as <#n>, and the end point of a line item is marked with the line item number as </#n>. The added text is typically highlighted with underline. Removed text is typically denoted with double strikeout marks (on the bottom for figure). Deleted figure is denoted with <#n>Delete</#n>, added figure is denoted with <#n>Add</#n> (may be nested in the tags with the same number). These markings are for highlight in the ballot only. They are not proposed to be included in the updated standard. Where the proposals show text extracted from the existing standard, any references in the text are aligned with current section numbering. However, recognize that various proposals may add or remove sections, requiring adjustment of references. This ballot assumes that SEMI will adjust these references prior to publication.


Doc. 5735 SEMI



Date: 5/7/23

Quotation from SEMI E171-0914SPECIFICATION FOR PREDICTIVE CARRIER LOGISTICS (PCL)

This Standard was technically approved by the Information & Control Global Technical Committee. This edition was approved for publication by the global Audits and Reviews Subcommittee on August 25, 2014. Available at www.semiviews.org and www.semi.org in September 2014.

1 Purpose1.1 The purpose of this Standard is to provide a communication scheme for exchanges of carrier logistics related information, especially predictive information, between equipment and the factory system in order to support seamless cascading of carriers for continuous processing of equipment in semiconductor fabrication systems or similar ones.

1.2 The purpose of this Standard is to provide models which represent carrier logistics management status in equipment to exchange predictive carrier logistics information in order to facilitate better synchronization with the factory system.

2 Scope2.1 This Standard defines a model which represents logistics management of a carrier in equipment as Carrier Logistics Job (CLJ). CLJ includes the following functionalities.

State management of logistics management of a carrier

Prediction management including submission, resubmission and withdrawal upon a change of predicted information such as time or load port assignment

Carrier ID assignment

Load port assignment

2.2 This Standard defines a model which represents management of multiple CLJs in equipment as Carrier Flow Job (CFJ). CFJ includes the following functionalities.

Order management of CLJs per process order

Prediction management of CLJs per carrier logistics order

Carrier scheduling

Load port scheduling including a queuing of multiple CLJs on one load port

Load port arbitration to CLJs for Internal Buffer Equipment

2.3 This Standard covers specifications for services to and events from CLJ and CFJ models.

2.4 This Standard covers PCL specifications for both Fixed Buffer Equipment and Internal Buffer Equipment.

2.5 This Standard covers compatibility with non-slot-integrity operation.

NOTICE: SEMI Standards and Safety Guidelines do not purport to address all safety issues associated with their use. It is the responsibility of the users of the Documents to establish appropriate safety and health practices, and determine the applicability of regulatory or other limitations prior to use.

3 Limitations3.1 On the Fly Control Purpose — This Standard is not for metrics (especially not for postmortem analysis) of waste times that may be contained in several time slots defined in this Standard due to the design of equipment and/or fab system. It only cares about synchronization between equipment and fab system. Those metrics should be standardized separately if needed.

3.2 Best Effort Basis — The requirements regarding prediction are on a best effort basis, as a prediction has limited accuracy in nature; moreover, in some cases prediction itself might not be provided.


Doc. 5735 SEMI



Date: 5/7/23

3.3 No Prediction Algorithm Covered — This Standard does not cover calculation algorithms for predictions.

3.4 Only for Critical Equipment — This Standard is intended to be used for equipment for which carrier logistics are critical, and, application of this Standard especially prediction portions may not be needed for equipment to which carrier logistics are not critical.

3.5 Not for Physical Synchronization of Load Port — This Standard is not intended to provide physical status of load ports.

4 Referenced Standards and Documents4.1 SEMI Standards and Safety Guidelines

SEMI E15 — Specification for Tool Load Port

SEMI E15.1 — Specification for 300 mm Tool Load Port

SEMI E30 — Generic Model for Communications and Control of Manufacturing Equipment (GEM)

SEMI E39 — Object Services Standard: Concepts, Behavior, and Services (OSS)

SEMI E40 — Standard for Processing Management (PM)

SEMI E62 — Specification for 300 mm Front-Opening Interface Mechanical Standard (FIMS)

SEMI E84 — Specification for Enhanced Carrier Handoff Parallel I/O Interface

SEMI E87 — Specification for Carrier Management (CMS)

SEMI E94 — Specification for Control Job Management (CJM)

4.2 ISO Standard1

ISO 8601:2004 — Internet Standard for Date/Time Format

NOTICE: Unless otherwise indicated, all documents cited shall be the latest published versions.

5 Terminology5.1 Abbreviations and Acronyms

5.1.1 AMHS — automated material handling system

5.1.2 CEW — Carrier Exchange Window

5.1.3 CFJ — Carrier Flow Job

5.1.4 CLJ — Carrier Logistics Job

5.1.5 FIMS — front-opening interface mechanical standard

5.1.6 FOUP — front opening unified pod

5.1.7 GEM — generic equipment model

5.1.8 PCL — Predictive Carrier Logistics

<#1>

5.1.9 PEC — Process Execution Collective

</#1>

<#4>

5.1.10 LR — load request

1 International Organization for Standardization, ISO Central Secretariat, 1, ch. de la Voie-Creuse, CP 56, CH-1211 Geneva 20, Switzerland; Telephone: 41.22.749.01.11, Fax: 41.22.733.34.30, http://www.iso.org


Doc. 5735 SEMI


http://www.iso.org/


Date: 5/7/23

5.1.11 LS — load stagnation

5.1.12 UR — unload request

5.1.13 US — unload stagnation

</#4>

5.2 Definitions

5.2.1 automated material handling system (AMHS) — an automated system to store and transport materials within the factory.

5.2.2 buffer — a set of one or more locations for holding carriers at or inside the production equipment.

5.2.3 carrier — a container, such as a FOUP or open cassette, with one or more positions for holding substrates.

5.2.4 Carrier Exchange Window (CEW) — a time slot which is allowed for a load port to unload a used carrier and then load a new carrier between AMHS without disturbing the continuous wafer processing of the equipment. Internal Buffer Equipment may have a CEW with multiple load ports to unload multiple used carriers and load multiple new carriers.

<#1>

5.2.5 carrier flow — a stream of carriers for one process thread which are loaded into the equipment, used by the equipment, and unloaded from the equipment.

5.2.6 Carrier Flow Job (CFJ) — a control action to manage multiple CLJs, which constitute one or more carrier flows, so that the equipment can continue processing seamlessly. Equipment may have multiple Carrier Flow Jobs.

</#1>

5.2.7 Carrier Logistics Job (CLJ) — a control action which manages entire logistics operation of one carrier from Load Queued to Unload Request. CLJ requests loading of a carrier, holds the carrier for use, and requests unloading of the carrier.

5.2.8 CarrierID — a readable and unique identifier for the carrier.

5.2.9 collection event — an event (or grouping of related events) on the equipment that is considered to be significant to the host.

5.2.10 docked position — the position where the carrier is ready for substrate extraction or insertion.

5.2.11 End of Load Request (EoLR) — a timing when Load Request state ends.

5.2.12 End of Unload Request (EoUR) — a timing when Unload Request state ends.

5.2.13 factory system — the control system of factory which includes the host and AMHS.

5.2.14 front-opening interface mechanical standard (FIMS) port — the substrate access port where the FOUP is opened and closed.

5.2.15 Fixed Buffer Equipment — production equipment that has only fixed load ports and no internal buffer for carrier storage. Substrates are loaded and unloaded directly from the carrier at the load port for processing.

5.2.16 host — the factory computer system or an intermediate system that represents the factory and the user to the equipment.

5.2.17 internal buffer — a set of locations within the equipment to store carriers. These locations exclude load ports.

5.2.18 Internal Buffer Equipment — equipment that uses an internal buffer.

5.2.19 load — the operation of placing a carrier on a load port.

5.2.20 load port — the interface location on the equipment where carriers are loaded and unloaded.


Doc. 5735 SEMI



Date: 5/7/23

<#4>

5.2.21 load stagnation — a stagnation caused by nonreadiness of a carrier to be loaded to the equipment. which loads substrates.

</#4>

5.2.22 nonproduction wafer (NPW) — a wafer which is used not for production but for tuning of equipment and its process performance.

5.2.23 object instantiation — the act of storing of information related to a physical or logical entity so that it can be recalled on demand based on its public identifier.

5.2.24 Predictive Carrier Logistics (PCL) — transportation control of carriers in a factory, which uses predictive information from composing elements to minimize delay due to the system inertia.

<#1>

5.2.25 Process Execution Collective (PEC) — a group of resources and its control logic in equipment, which execute one complete process thread of substrate(s) starting with extraction from carrier and ending with insertion to carrier, and do not share at least load carrier(s) or unload carrier(s) with other process thread(s).

</#1>

5.2.26 process equipment — equipment used to produce product, such as semiconductor devices. This excludes metrology and material handling equipment.

<#1>

5.2.27 process thread — sequentially performed actions that process substrate(s) starting with extraction from carrier and ending with insertion to carrier in equipment. Process thread consists of actions such as transportation, processing and measurement.

</#1>

5.2.28 production equipment — equipment used to produce product, such as semiconductor devices, including substrate sorting, process, and metrology equipment and excluding material handling equipment.

5.2.29 properties — a set of name value pairs assigned to an object or used in a service message to include additional information about the object (e.g., carrier, port, etc.).

5.2.30 reinitialization — a process where production equipment is either powered off then powered on or when some kind of hardware or software reset is initiated to cause the equipment to reset and possibly reload its software. On production equipment that contains some kind of mass storage device this can also be called a ‘reboot’.

5.2.31 single communication connection — exactly one physical connection using exactly one logical session and a standard set of messages.

5.2.32 slot map –– the information that relates which slots in a carrier hold substrates, both correctly and incorrectly.

<#1>

5.2.33 stagnation — a status of a carrier flow Process Execution Collective (PEC), which shows that the equipment PEC is ready to perform a substrate process, but is forced to stop due to nonreadiness of a carrier which loads or unloads substrates.

</#1>

5.2.34 standard message set — messages conforming to standard message specifications.

5.2.35 Start of Load Request (SoLR) — a timing when Load Request state starts.

5.2.36 Start of Unload Request (SoUR) — a timing when Unload Request state starts.

5.2.37 substrate — material held within a carrier. This can be product, or durables such as reticles.


Doc. 5735 SEMI



Date: 5/7/23

5.2.38 undocked — the status of a carrier on a load port or in an internal buffer that is not at the docked position.

5.2.39 unload — the operation of removing a carrier from a load port.

<#4>

5.2.40 unload stagnation — a stagnation caused by nonreadiness of a carrier which should be unloaded from the equipment. unloads substrates. Unload stagnation may occur when the carrier for unload is different than the one used for load. When slot integrity is maintained and the carrier remains on the load port, unload stagnation does not occur.

</#4>

6 Conventions6.1 Objects

6.1.1 Whenever the equipment is required to know about specific kinds of entities and required to manage information concerning these entities, it is useful to treat these entities as objects that comply with the basic requirements of SEMI E39 Object Services Standard (OSS). This is especially true whenever there are a large number of objects of a given type or when the entities are transient rather than permanent. In both cases, it is difficult to describe a general way for the host and equipment to specify which particular entity is referenced and to get information related only to a specific one out of many.

6.1.2 By defining these entities as objects that comply with OSS, it is only necessary for the host to specify the type of object and its specific identifier in order to inquire about one or more properties of the specific entity of interest.

6.1.3 Object Properties

6.1.3.1 A property (attribute) is information about an individual object that is presented as a name and value pair. The name is a formally reserved text string that represents the property, and the value is the current setting for that property.

6.1.3.2 Properties shall be accessible to the host via the service GetAttr. Using SEMI E39 Object Services Standard, for example, it is possible to:

get the list of IDs for the current objects at the equipment, and

get the specified properties for one or more individual objects.

6.1.4 Rules for Object Properties

Attributes with RO (Read Only) access cannot be changed using SetAttr service as defined in OSS.

Attributes with RW (Read/Write) access can be changed using SetAttr service as defined in OSS.

Additional attributes may be specified by the user or the equipment supplier by using an attribute name starting with ‘UD’ (User Defined). Care should be taken to ensure the name of the attribute is unique.

6.1.5 Object Attribute Table

6.1.5.1 The object attribute table is used to list all the attributes related to the defined object as shown below. The access is defined as Read Only (RO) or Read/Write (RW). The Reqd column is used to specify whether the attribute is required <#2> (Y), conditional (C), or optional (O) </#2> for implementation. Finally, the Form column is used to specify the format of that particular attribute.

Table 1 Object Attribute Table

Attribute Name Definition Access Reqd Form

<#2> ObjType Object type RO Y Text = ‘Carrier’ </#2>

6.2 State Model Methodology


Doc. 5735 SEMI



Date: 5/7/23

6.2.1 A state model consists of four elements: a State Model Diagram, a State Model Definition Table, a State Definition, and a State Transition Table.

6.2.2 State Model Diagram — The diagram of the state model uses the Harel State Chart notation. An overview of this notation is presented in an Appendix of SEMI E30. The definition of this notation is presented in Science of Computer Programming 8, “Statecharts: A Visual Formalism for Complex Systems,” by D. Harel, 1987.2

6.2.3 State Model Definition Table — The State Model Definition Table used in this Standard has the following format. This table defines states and possible transition(s) from each state side by side. Each state has one or more transitions. When the transition comes from outside this table, the state definition column associated with the transition may be blank (see #1). When the transition comes from unspecified multiple states with the same condition, the state definition column may say “#Any state,” and there may not be an explicit transition number.

6.2.3.1 Definition of State — Columns under the State column define States with No. (Number), Name and Abstract of Definition. ‘No.’ corresponds to the state number in the associated state diagram. ‘Name’ defines a name of each state. ‘Abstract of Definition’ provides an abstract of the State Definition in the State Definition Table.

6.2.3.2 Definition of Transition — Columns under the Transition column define Transitions with No. (Number), Abstract of Trigger, Abstract of Action, New State, and Comments. ‘No.’ corresponds to transition number in the associated state diagram. ‘Abstract of Trigger’ and ‘Abstract of Action’ provide abstracts of the Trigger and Action in the State Transition Table accordingly. ‘New State’ defines a state number to move to after the transition is completed by pointing to one of the states defined in the state definition in left side of the table. The Comment column may be used to put comments to each transition or their From state.

Table 2 State Model Definition Table

State Transition

No. Name Abstract of Definition No. Abstract of Trigger Abstract of Action New State

Comments

-#1 -#1 -#1 T00 S00Snn#2 # Any state#2 -#2 - S03S00 T01 S01S04#3 T02 S00

S01 T03 S02T04 S03

S02 T05#4 S00

S10#5 - - - -S11 T10 S12S12 T11 S11

S03 T06 S00#1 When the transition comes from outside of this table, the state definition column may be blank.#2 When the transition comes from unspecified multiple states with the same condition, the state definition column may say ‘#Any state’.#3 A state which has substates.#4 One transition path has multiple cases (trigger and action pairs).#5 A state separated by a dotted line is a parallel state of the state above.

6.2.4 State Definition Table — State definition tables are provided in conjunction with the state diagrams to explicitly describe the definition of each state. A state definition table contains columns for State Number, Mnemonic, State Definition, and Comments.

2 Elsevier Science, P. O. Box 945, New York, NY 10159-0945; http://www.journals.elsevier.com/science-of-computer-programming/


Doc. 5735 SEMI


http://www.journals.elsevier.com/science-of-computer-programming/


Date: 5/7/23

Table 3 State Definition Table

No. Mnemonic State Definition Comments

6.2.5 State Transition Table — State Transition Tables are provided in conjunction with the state diagrams to explicitly describe the nature of each state transition. A State Transition Table contains columns for Transition Number, Previous State, Trigger, New State, Actions, and Comments. The ‘trigger’ (column 3) for the transition occurs while in the Previous State. The ‘Actions’ (column 5) includes a combination of:

Actions taken upon exit of the previous state,

Actions taken upon entry of the new state, and

Actions taken which are most closely associated with the transition.

Table 4 State Transition Table

No. Previous State Trigger New State Actions Comments

6.2.6 State Model Requirements

6.2.6.1 Requirement — The state models included in this Standard are a requirement for compliance. Equipment shall maintain state models for each of the required state models as defined in this Standard. Equipment shall maintain individual and unique state models for each logical entity instantiated or each physical entity in the equipment that has associated state models.

6.2.6.2 Representation as the Host View — A state model represents the host’s view of the equipment, and does not necessarily describe the internal equipment operation. All state model transitions shall be mapped sequentially into the appropriate internal equipment collection events that satisfy the requirements of those transitions. In certain implementations, the equipment may enter a state and have already satisfied all of the conditions required by the state models in this Standard for transition to another state. In this case, the equipment makes the required transition without any additional actions.

6.2.6.3 Additional Substates — Some equipment may need to include additional substates other than those in this Standard. Additional substates may be added, but shall not change the defined state transitions in this Standard. All expected transitions between states in this Standard shall occur.

6.2.6.4 Uniqueness of Event Identifier — The event identifier reported during a particular state transition change for each of these state models shall be shared for all associated state models but unique for each transition. For example, if the equipment has two load ports and the load port state model defines ten transitions, there must be exactly ten event identifiers for each load port transfer state model but not ten for each physical load port. The information identifying the physical entity or logical entity undergoing the transition will be contained within the associated event report.

6.2.6.5 Events — All state transitions in this Standard, unless otherwise specified, shall correspond to collection events. More explicitly, there must be a unique collection event for each state transition.

6.2.6.6 Events for Multiple AND Substates — When a state model is defined with multiple AND substates, the equipment may report all state entry events with only one collection event.

6.2.6.7 Events for Conditional Path — When conditional paths are defined in the state model, it is not necessary to report any state transition(s) until a terminal state is reached at which time each transition used to reach that state is reported.

6.3 Object


Doc. 5735 SEMI



Date: 5/7/23

6.3.1 Recognition of Object — From the host point of view, an object is instantiated if the host is able to query the equipment about that object, its current state, and other attributes. Once instantiated, the object is considered destroyed (no longer instantiated) if the response to such queries is ‘unknown object’.

6.3.2 Object Identifier (ObjID) — The purpose of an Object Identifier is to allow references to an object within the system. The Object Identifier is assigned when an object is instantiated and should be unchanged or persistent until the end of the object lifecycle. The Object Identifier shall be unique at the equipment during lifecycle of the object.

6.4 Services

6.4.1 Definition of Service — Services are functions or methods that may be provided by either the equipment or the host. A service message may be either a request message, which always requires a response, or a notification message that does not require a response.

6.4.1.1 Notification Message Service — Notification type messages are initiated by the service provider (e.g., the equipment) and the provider does not expect to get a response from the service user.

6.4.1.2 Request Message Service — Request messages are initiated by a service user (e.g., the host). Request messages ask for data or an activity from the provider. Request messages expect a specific response message (no presumption on the message content).

6.4.2 Service Message Description — A service message description table defines the parameters used in a service, as shown in the following table:

Table 5 Service Message Description Table

Service Name Type#1 Description

#1 Type can be either ‘N’ = Notification or ‘R’ = Request & Response.

6.4.3 Service Message Parameter Definition — A service parameter dictionary table defines the description, range, and type for parameters used by services, as shown in the following table:

Table 6 Service Message Parameter Definition Table

Parameter Name Form Description#1

#1 A row is provided in the table for each parameter used on a service.

6.4.4 Service Message Definition — A service message description table defines the parameters used in a service message, and describes each message and its cause/effect to the equipment, as shown in the following table:

Table 7 Service Message Definition Table

Service Parameter Req/Ind Rsp/Conf Description

6.4.4.1 Definition of Req/Ind and Rsp/Conf Columns — The columns labeled Req/Ind and Rsp/Conf link the parameters to the direction of the message. The message sent by the initiator is called the ‘Request’. The receiver terms this message the ‘Indication’. The receiver may then send a ‘Response’, which the original sender terms the ‘Confirmation’.


Doc. 5735 SEMI



Date: 5/7/23

6.4.4.2 Definition of Codes for Req/Ind and Rsp/Conf Columns — The following codes appear in the Req/Ind and Rsp/Conf columns and are used in the definition of the parameters (i.e., how each parameter is used in each direction):

Table 8 Codes For Req/Ind and Rsp/Conf Columns

M Mandatory Parameter – must be given a valid valueC Conditional Parameter – may be defined in some circumstances and undefined in others. Whether a value is given may

be completely optional or may depend on the values of other parameters.U User-Defined Parameter- The parameter is not used= (for response only) Indicates that the value of this parameter in the response must match that in the primary (if defined)

6.5 Variable Data Definitions

6.5.1 Variable data definitions define variable data requirements. Values of these variables are available to the host via collection event reports and host status queries.

6.5.2 Event Report Requirement — The identifier of an object and all of the attributes of that object shall be available for inclusion in event reports associated with that object.

6.5.3 Object Attribute Variable in Non-Extinction Event — The object attribute variables in event reports linked to non-extinction event(s) shall contain the values of the attributes after the transition. This requirement allows the receiver of the report to know the current condition of the object.

6.5.4 Object Attribute Variable in Extinction Event — The object attribute variables in event reports linked to extinction event(s) shall contain the values of the attributes before the transition unless it is specifically stated that the destruction transition modifies the attribute value. This requirement allows the receiver of the report to know the final condition of the object at the time it was deleted.

6.5.5 Subscripted variables are used either as items within a list or to differentiate data representing different entities. Subscripted variables are always valid.

6.5.6 Table Format — The following table defines variable data that shall be provided by the production equipment.

Table 9 Variable Data Definitions

Variable Name Description Type Access Comment

7 PCL Conceptual Descriptions7.1 Conceptual Descriptions — This chapter defines and describes a concept of PCL. This chapter does not contain any requirements.

7.2 Load/Unload Readiness on Load Port and Relationship with SEMI E87 — In order to avoid conflicts and to be coexistent with SEMI E87 CMS, this Standard only provides a scheduling information of carrier logistics, and does not represent physical readiness for Load/Unload which is covered by SEMI E87.

7.3 Key Timings for Carrier Logistics — There are four key timings for carrier logistics between equipment and the factory system. PCL focuses on providing these timings and their predictions as shown below. (See definition of PCL for state names.)

<#4>


Doc. 5735 SEMI



Date: 5/7/23

7.3.1 Basic Timings — There are two key timings and their predictions for carrier logistics between equipment and the factory system.

SoUR (Start of Unload Request): Timing when a carrier completes and requests its unload is requested.

EoLR (End of Load Request): Timing when a carrier is loaded

UR (Unload Request) Prediction: Predicted timing when a carrier completes and its unload is requested

LS (Load Stagnation) Prediction: Predicted timing by which a carrier has to be loaded to avoid not cause stagnation

<#4>Delete</#4>

<#4>Add</#4>

Figure 1Key Timings for PCL

7.3.2 Additional Timings — There are two additional key timings and their predictions, mainly for Internal Buffer Equipment.

SoLR (Start of Load Request): Timing when a carrier load is requested

EoUR (End of Unload Request): Timing when a carrier is unloaded

LR (Load Request) Prediction: Predicted timing at which Load Request state starts. This prediction is introduced to indicate the predicted timing at which the equipment requests loading of a carrier for the CLJ. Note that the physical readiness of load port to load the carrier should be confirmed via SEMI E87.

US (Unload Stagnation) Prediction: Predicted timing by which the a carrier haves to be unloaded to avoid not cause stagnation. US Prediction is used when there is no subsequent Load Request or Unload Request which implies Unload Stagnation Prediction timing to the host (or AMHS). For example, Load Stagnation Prediction of subsequent Load Request on the same load port implies that the Unload Request and the subsequent Load Request should be completed by the predicted time given by the Load Stagnation Prediction, so, US Prediction is not required.


Doc. 5735 SEMI



Date: 5/7/23

<#4>Delete</#4>

<#4>Add</#4>Figure 2

Additional Key Timings for PCL</#4>

7.4 Introduction of Carrier Logistics Job (CLJ) — In order to model the logistics control of a carrier, including the key timings and their predictions, this Standard introduces CLJ, which represents each carrier’s logistics control. CLJ models the management process of a carrier from the request for a new carrier to sending the carrier as shown below.

<#4>

Load Queued: This state is introduced mainly for Internal Buffer Equipment to represent the situation in which Load Request Prediction or Load Stagnation Prediction is done, however the equipment is not capable to accept a carrier for the prediction yet (typically because no space is available in Internal Buffer yet). In case CLJs are assigned to load ports in order by their predicted times and there is no possibility of dead lock, Load Request state may be used instead of Load Queued state for simplicity. See Application note for Internal Buffer Equipment in Appendix for an example.

Load Request: This state is introduced to represent the situation in which the equipment is requesting load of a carrier. Load Stagnation Prediction, Unload Request Prediction, or Unload Stagnation Prediction may also be done. This state does not always mean physically ready to load.

Carrier Valid: A carrier is loaded and not completed yet by the equipment. Unload Request Prediction or Unload Stagnation Prediction may also be done.

Unload Request: The equipment is requesting unload of the carrier. Unload Stagnation Prediction may also be done. This state does not always mean physically ready to unload. In Internal Buffer Equipment, the carrier may still be in Internal Buffer.

</#4>


Doc. 5735 SEMI



Date: 5/7/23

<#4>Delete</#4>


States and Predictions of CLJ Object

7.5 Introduction of Carrier Exchange Window (CEW) — Because the resources of equipment are limited, the number of carriers which can reside in the equipment is also limited. So, in normal cases, loading of new carriers follows after unloading of used carriers. These timings form a window in which AMHS should exchange those carriers.

7.5.1 Definition of CEW — See Terminology section.

7.5.2 CEW for Fixed Buffer Equipment — In Fixed Buffer Equipment, loading of a new carrier follows after unloading of a used carrier on each load port. Normally, during CEW, other load ports hold required carriers for cascading of wafers. A carrier has overhead times such as confirmation of carrier ID, opening of the door, confirmation of wafer existence on slots, and creation of process job before the wafers become ready for process, overhead times such as closing of the door, purging with inert gas, and undock after the process completion, and equipment has a wafer queue. Due to those overhead times, Carrier Valid requires Handover Periods. The Handover Period is determined by equipment according to its configuration and operation.

<#4>

<#4>Delete</#4>


Doc. 5735 SEMI



Date: 5/7/23

<#4>Add</#4>

Figure 4Definition of CEW in Two Load Port Fixed Buffer Equipment

<#4>Add</#4>

Figure 5Definition of CEW in Three Load Port Fixed Buffer Equipment

</#4>

7.5.3 CEW for Internal Buffer Equipment — In Internal Buffer Equipment, loading of new carriers may follow after unloading of used carriers on multiple load ports. Normally, during CEW, internal buffers hold required carriers for cascading of wafers.

<#4>

7.5.3.1 CLJs and CEW — CLJs which form a batch may typically be dealt as a group. Predictions may be done at the same time; however the predicted times for those CLJs may be different according to the structure of the equipment. In the example shown in the following figure, currently, Unload Request Predictions of CLJs which form Batch 0 (CLJ 0 through CLJ 3) are already done. At the timing of Batch 1 formation, Unload Request Predictions of CLJ 4 through CLJ 7 are done, and just after them, to make Batch 2 formed by then, Load Stagnation Predictions of CLJs for Batch 2 (CLJ 8 through CLJ 11) may be calculated. Thus, the Unload Request Predictions for Batch 0 and Load Stagnation Predictions for Batch 2 form CEW. The timing, when Unload Request state ends and Load Queued state changes to Load Request state, depends on the timing when AMHS completes the unload.


Doc. 5735 SEMI



Date: 5/7/23

<#4>Add</#4>

Figure 6CLJs and CEW in Typical Internal Buffer Equipment

</#4>

<#4>

7.5.3.2 Load Port View of CLJs and CEW — CLJs may be assigned to load ports as shown in the following figures. In the case of Bi-Direction, two load ports are used to unload four carriers, then, to load four carriers. In the case of Uni-Direction, one load port is used to unload four carriers, and another load port is used to load four carriers. This standard supports scheduling aspect and actual (physical) readiness of carrier load/unload on load port should be controlled by using SEMI E87 and SEMI E84.

<#4>Delete</#4>

<#4>Add</#4>

Figure 7Definition of Load Port View of CLJs and CEW in Internal Buffer Equipment (Bi-Direction)


Doc. 5735 SEMI



Date: 5/7/23

<#4>Add</#4>

Figure 8Load Port View of CLJs and CEW in Internal Buffer Equipment (Uni-Direction)

</#4>

7.6 Introduction of Carrier Flow Job (CFJ) — In order to define the relationship between CLJs, this Standard introduces CFJ, which manages a carrier flow. CFJ manages the order of CLJs and predicted timings, etc.

<#1>Delete</#1>

<#1>Add</#1>

Figure 9Image of Data Provided by CFJ

7.7 Scalable Specifications — In order to enable gradual application to the existing designs, this Standard provides building blocked scalable specifications. Examples are shown in the following table. See Appendices for explanations.

<#4>


Doc. 5735 SEMI



Date: 5/7/23

Table 10 Scalability

Name Type#1 Main States#2 Predictions Assignment#3 Notes

FB IB LQ LR CV UR SoLR EoLRLS

SoUR EoURUS

LP CID

Interim A - - - R R - - R - - - SoUR Prediction onlyLP-Based A - - R R - - R R - - - Load port by load portBasic A - - R R - - R R - R O Basic for Fixed BufferBi-Direction - A - R R R - R R - R R Bi-Direction Internal BufferUni-Direction - A R R R R R R R R R R Uni-Direction Internal Buffer

</#4>#1 FB = Fixed Buffer Equipment, IB = Internal Buffer Equipment.#2 LQ = Load Queued, LR = Load Request, CV = Carrier Valid, UR = Unload Request.#3 LP = Load Port, CID = Carrier ID.#4 A = Applicable, R = Required, O = Optional, - = Not required.

<#1>

7.8 Introduction of Process Execution Collective (PEC) — Equipment is not always executing a single thread of process. Some equipment has a capability to execute multiple process threads simultaneously. In such cases, the key timings should be managed separately per process thread. In order to manage the key timings per process thread, this Standard introduces PEC.

7.8.1 Definition of PEC — See Terminology section.

7.8.2 Description of PEC — Multiple PECs do not share the same carriers for both load and unload. Process threads which share the same carriers for both load and unload shall be dealt as parallel portions in one PEC, because those process threads also share the same stagnation condition and timing. Process threads of substrates start from and end at carriers on FIMS ports. A FIMS port is located at the load port in Fixed Buffer Equipment, and located at an internal FIMS port in Internal Buffer Equipment. PECs are not always completely independent in their resources, and may share some of the resources with other PECs. See the following figure for examples.

Example 1 shows one PEC which has mutually dependent parallel process threads, as both the solid lined path and dotted lined path use the same carrier for both load and unload, and stagnation timings are not independent. For continuous processing during AMHS access, one more carrier on another load port may be assigned alternately.

Example 2 shows two PECs which share the same carrier for load, and use different carriers for unload, so unload stagnation timings are independent.

Example 3 shows two completely independent PECs.

Example 4 shows two PECs which have different process steps and share some wafer paths such as load locks.

<#1>Delete</#1>

Figure 10Examples of PEC


Doc. 5735 SEMI



Date: 5/7/23

</#1>

7.9 Relationship of the Entities in PCL — The CLJ and CFJ objects have relationships shown in the following figure.

<#1>Delete</#1>

<#1>Add</#1>

Figure 11Relationship Model of CFJ and CLJ Objects

<#4>

7.10 Cascading of CLJ Objects — For seamless cascading of wafer process, the Carrier Valid states of consecutive CLJs mapped on multiple load ports should have required overlap which is determined by the equipment. This overlap is typically caused by the carrier handling overheads, such as dock, door open, wafer mapping, door close, inert gas purge, and undock and wafer queue in the equipment. The Unload Request state of a CLJ and Load Request state of a subsequent CLJ assigned to the same load port share the same CEW.

</#4>

<#4>Delete</#4>


Doc. 5735 SEMI



Date: 5/7/23

Figure 12Queuing of CLJ Objects and CEW (Two Load Ports)

<#4>Delete</#4>

Figure 13Queuing of CLJ Objects and CEW (Four Load Ports)

8 PCL Requirements8.1 PCL Requirements — The PCL Standard defines the behavior, data, and services required for the following objects of equipment. This Standard provides a standard interface for host/equipment communications regarding the following information.

8.1.1 Carrier Flow Job (CFJ) Object — CFJ is defined in the section ‘Carrier Flow Job (CFJ) Requirements.’

8.1.2 Carrier Logistics Job (CLJ) Object — CLJ is defined in the section ‘Carrier Logistics Job (CLJ) Object Requirements.’

8.2 Reporting Scheme of Time for PCL — Every PCL event or service reports the timing as a combination of current time of the equipment clock and predicted time per the equipment clock in order to be free from a time difference problem between the host and equipment. The host is strongly recommended to compare the host clock and equipment clock, and to understand the reported time per equipment clock in host time per host clock.

8.3 Prediction Resubmission Threshold for PCL — PCL allows resubmission of predictions to report updated value. However, in order to avoid too many resubmissions, resubmission can only be made when the new value satisfies PTimeSensitivity and PTimeSenseDB definitions.

8.4 PCL Variable Data Definitions — This section defines variable data requirements for PCL. Values of these variables are available to the host via collection event reports and host status queries.

Table 11 PCL Variable Data Definitions


PCLActive Activate PCL functionality.PCLActive = PCL functionality is ActivePCLInactive = PCL functionality is InactiveDefault is PCLInactive.

Enumerated:PCLActive, PCLInactive

RW This determines whether CFJ and CLJ are active or inactive.


Doc. 5735 SEMI



Date: 5/7/23


PTimeSensitivity Sensitivity to decide resending of predicted times defined in this Standard. The purpose of this variable is to prevent too frequent resends. Predicted times shall not be resent if the change of remaining time is smaller than this percentage.

Positive integer [%] RW While the duration from current time to the predicted time is long, small changes are not important.The predicted time is expected to become precise when the duration becomes shorter.

PTimeSenseDB Dead-band of sensitivity to resend predicted time. The purpose of this variable is to prevent too frequent resends. Predicted times shall not be resent if the change of remaining time is smaller than this value.

Positive integer [sec] RW It is meaningless to resend small changes to which the factory system, including the host and AMHS, cannot respond.

8.5 TimeReport — This section defines the format, which is used to report a time in this Standard, by using ISO 8601:2004. TimeReport information shall be reported as specified in this section.

YYYY-MM-DDThh:mm:ss.sTZD (e.g., 2014-04-11T15:30:20.34+08:00)

Table 12 Definition of TimeReport

Identifier Description

YYYY Four-digit yearMM Two-digit month (01 = January through 12 = December)DD Two-digit day of month (01 through 31)T Special separator character (‘T’) used between date and timehh Two digits of hour (00 through 23) (am/pm NOT allowed)mm Two digits of minute (00 through 59)ss Two digits of second (00 through 59)s One or more digits representing a fraction of a secondTZD time zone designator (Z, +hh:mm, or –hh:mm)

9 Carrier Flow Job (CFJ) Object Requirements9.1 CFJ Object Definition

9.1.1 Definition of CFJ Object — The CFJ object is a software representation of the carrier flow management in the equipment. CFJ manages multiple CLJs which constitute one <#1> or more carrier flows </#1>. Information about CFJ is encapsulated as an object. This allows the host to exchange information with the equipment about one or more specific CFJs by using services defined in SEMI E39 Object Services Standard.

9.1.2 Number of CFJs — Equipment may create multiple CFJs when the equipment manages multiple carrier flows separately per load port. CFJ can be assigned to each load port, to a group of load ports, or to whole equipment depending on the operation of the equipment. (See Appendices for examples.)

9.2 CFJ Object Descriptions

9.2.1 CFJ Object Instantiation — Under normal circumstances, CFJ object is instantiated by the equipment when the equipment is started up.

9.2.2 CFJ Object Identifier (ObjID) — The CFJID is the CFJ Object Identifier. The equipment is responsible for ensuring uniqueness of the CFJID prior to instantiation.

9.2.3 CFJ Object Destruction — A CFJ Object reaches the end of its lifecycle when the equipment is shut off.


Doc. 5735 SEMI



Date: 5/7/23

9.2.4 CFJ Object Persistence — A CFJ Object may persist over equipment shut down to restart if the carriers still stay in the equipment. Capability to perform this persistence automatically is dependent on equipment design. In any case, when equipment moves into host control with carriers on it, CFJs which represent the carriers shall be created.

9.3 CFJ Object Functional Requirements

9.3.1 Order Management of CLJs — CFJ maintains an ordered list of CLJs. CLJs shall be listed in order of associated wafer access—the CLJs in Unload Request state first, the CLJs in Carrier Valid state, the CLJs in Load Request state, and then the CLJs in Load Queued state. In the same state, CLJs with earlier wafer access shall be listed in higher order. When the order of wafer access is changed, the order of the CLJs in the CFJ shall be aligned to the order.

9.3.2 Load/Unload Timing Management of CLJs — CFJ maintains predicted timings of CLJs. CFJ reflects the calculation result of Predictions. This Standard does not define the prediction algorithm or calculation timing.

9.3.3 Load Port Assignment to CLJs — CFJ performs load port scheduling and assigns load port to CLJs.

9.3.3.1 Load Port Assignment for Fixed Buffer Equipment — Normally, the load ports used in Load Request and Unload Request states of one CLJ are the same one, and the carrier stays on the same load port all the time. In some cases, a load port may not be assigned at the timing of CLJ creation.

9.3.3.2 Load Port Assignment for Internal Buffer Equipment — Normally, the load ports used in Load Request state and Unload Request state of one CLJ are independent, and the carrier stays on an internal buffer for most of the time. A load port may or may not be assigned at the beginning of Load Request state or Unload Request state.

9.3.3.2.1 Speculative Assignment of Load Port and On-the-Fly Arbitration — Multiple CLJs may be assigned to the same load port, and final arbitration may be done by the arrival order information from AMHS. This Standard does not define the arbitration algorithm.

9.4 CFJ Object Attribute Definitions — The following table defines the attributes of CFJ Object.

9.4.1 Attributes Maintenance — All attributes in the following table are always maintained and updated by the equipment.

Table 13 CFJ Object Attribute Definition

Attribute Name Definition Access#1 Reqd Form

ObjID CFJ object identifier RO Y TextCFJID. Numerical text expression of positive integerObjID is equipment defined

ObjType Object Type RO Y Text = “CarrierFlowJob”MaxCarrierNumber Maximum number of carriers the CFJ

can handleMaximum number of CLJs with a carrier which is physically assigned (loaded)

RO Y Positive integer

CFJData Ordered list of attributes of CLJs RO Y Ordered list of:CLJ attributes: Defined in CLJ

#1 Even though a value may be marked as RO (read only), the initial value for the attribute may be provided by the host.

9.5 CFJ State Model — The following diagrams and tables define the state model of CFJ object. Equipment shall maintain an appropriate number of CFJs.

9.5.1 CFJ State Model Diagram


Doc. 5735 SEMI



Date: 5/7/23

Figure 14CFJ State Model Diagram

9.5.2 CFJ State Model Definition

Table 14 CFJ State Model Definition

State Transition

No. Name Abstract of Definition

No.#1 Abstract of Trigger

Abstract of Action#2

New State

Comments

- - (No state) Tf00 Equipment is started Create CFJ Sf01Sf00 CFJ Created CFJ is created - - - -

Sf01 CFJ Inactive CFJ is not active Tf01 Activation of CFJ function is done

CFJ Event Sf02

Sf02 CFJ Active CFJ is activeCFJData is valid

Tf02 CFJData change occurred CFJ Event Sc03Tf03 Set CFJ to inactive CFJ Event Sc01

#1 Numeric portion of the transition numbers in this column shall be used as event numbers.#2 Events in the Action column report following information. CFJ Event reports CFJID and CFJData.

9.5.3 CFJ State Definition Table

Table 15 State Definition Table


Sf00 CFJ Created A state in which a CFJ is created and in operation.Sf01 CFJ Inactive CFJ is inactive. CLJ is also inactive.

PCL functionalities are not used.Sf02 CFJ Active CFJ is active. CLJ is also active.

PCL functionalities are used.

9.5.4 CFJ State Transition Table

Table 16 CFJ State Transition Table

No.#1 Previous State Trigger New State Actions#2 Comments

Tf00 (No state) Equipment started CFJ Inactive Create CLJ


Doc. 5735 SEMI



Date: 5/7/23


Tf01 CFJ Inactive Activate CFJ and CLJ to start use of PCL functionalities

CFJ Active CLJ Event

Tf02 CFJ Active Any change in CFJData CFJ Active CFJ EventTcf3 CFJ Active Inactivate CFJ and CLJ to stop use of

PCL functionalitiesCFJ Inactive CFJ Event

#1 Numeric portion of the transition numbers in this column shall be used as event numbers.#2 Events in the Action column report following information. CFJ Event reports CFJID and CFJData.

9.6 CFJ Services — This section defines the message services required to support CFJ functionalities.

9.6.1 CFJ Service Message Description — The following table is a list of CFJ services.

Table 17 CFJ Service Message Description


GetCFJList R This service gets a list of the CFJ object from the equipment.Use SEMI E39 OSS to get ObjIDList by specifying ObjType and ObjID for ATTRID.

GetCFJData R This service gets CFJData attribute of CFJ from the equipment.Use GetAttr service of SEMI E39 OSS for this purpose.

PutAMHSArrivalInfo R Optional mainly for Internal Buffer Equipment.This service puts AMHS service information to the equipment.

#1 The ‘Type’ column is used to indicate whether the service consists of a request/response message pair, ‘R’, or a single notification message, ‘N’.

9.6.2 CFJ Service Message Parameter Definition — The following is a list of required parameters used in conjunction with CFJ service messages.

Table 18 CFJ Service Message Parameter Definition

Parameter Name Form Description

CFJList List of CFJID List of CFJIDCFJID Text ID of CFJCFJData Ordered list of:

CLJ attributes: Defined in CLJVariable Data of CFJ

AMHSArrivalInfo Ordered list of: Structure: CLJID EstimatedArrivalTime

Optional Arrival information of AMHS mainly for Internal Buffer Equipment.

9.6.3 CFJ Service Message Definitions — The following tables specify the allowable/required parameters for each service.

9.6.3.1 PutAMHSArrivalInfo — This service is used to inform the arrival order and estimated timings of AMHS vehicles assigned for the CLJs to CFJ.


Doc. 5735 SEMI



Date: 5/7/23

Table 19 PutAMHSArrivalInfo Service Parameter Definitions

Parameter Name Req/Ind Rsp/Conf Description

CFJID M - ID of CFJAMHSArrivalInfo M - Arrival information of AMHS vehiclesEquipmentResponse - M Reply from Equipment

9.7 CFJ Variable Data Definitions — This section defines variable data requirements for CFJ. Values of these variables are available to the host via collection event reports and host status queries.

Table 20 CFJ Variable Data Definitions


CFJID ObjID of CFJCFJID is equipment defined

Numerical text expression of positive integer

RO

MaxCarrierNumber Maximum number of carriers the CFJ can handleMaximum number of CLJs with a carrier physically assigned

Positive integer RO

CFJData Ordered list of attributes of CLJs

Ordered list of: CLJ attributes: Defined in CLJ

RO Event is sent upon any change

10 Carrier Logistics Job (CLJ) Object Requirements10.1 CLJ Object Definition

10.1.1 Definition of CLJ Object — The CLJ object is a software representation of the carrier logistics control in the equipment. Information about CLJ is encapsulated as an object. This allows the host to exchange information with the equipment about one or more specific CLJs by using services defined in SEMI E39 Object Services Standard.

10.1.2 Handoff Readiness on Load Port and CLJ — Load Request and Unload Request states, or Load Port Assignment parallel states only provide a schedule among multiple CLJs, and do not represent physical readiness for handoff. Load Port state of E87 shall be used to ensure physical readiness of the load port for handoff.

10.1.3 Number of CLJ Objects — Equipment may create multiple CLJs in order to feed substrates continuously through its process modules. The number of CLJs depends on the structure of the equipment and the depth of predictions.

1: In principle, equipment normally has two CLJs per one carrier position where a carrier can nontemporarily reside in the equipment, one is the CLJ which currently occupies the carrier position, and the other is the CLJ which is queued to the carrier position. Generally, the carrier positions are load ports in Fixed Buffer Equipment, and internal buffers for Internal Buffer Equipment. Note that, in general, the load ports of Internal Buffer Equipment are not counted in carrier positions where a carrier can nontemporarily reside as they are in the critical path between AMHS and internal buffers and used as temporary positions to handoff carriers to and from AMHS. When equipment uses its load ports as nontemporary carrier positions, they are counted as carrier positions. In other words, normally, Fixed Buffer Equipment expects the same number of CLJs with the number of load ports as currently assigned jobs and another same number of CLJs as the next jobs Internal Buffer Equipment expects the same number of CLJs with the number of internal buffers (and internal FIMS ports) as currently assigned jobs and another same number of CLJs as the next jobs.

10.2 CLJ Object Descriptions

10.2.1 CLJ Object Instantiation — Under normal circumstances, CLJ object is instantiated by the equipment when the equipment recognizes a requirement to deal with a carrier.

10.2.1.1 Host Triggered Instantiation — An instantiation which is triggered by the host. The host may request as many CLJ creations as the host plans in order to give predictive information to the equipment. The equipment


Doc. 5735 SEMI



Date: 5/7/23

creates those CLJs and manages the execution order of them by communicating with the host. This Standard does not define the algorithm to decide the order.

10.2.1.2 Equipment Triggered Instantiation — An instantiation which is triggered by the equipment. A CLJ object is instantiated when the equipment recognizes that <#1> the equipment a PEC </#1> can receive new carrier.

10.2.2 CLJ Object Identifier (ObjID) — The CLJID is the CLJ Object Identifier. The equipment is responsible for ensuring uniqueness of the CLJID prior to instantiation.

10.2.3 CLJ Object Destruction — A CLJ Object reaches the end of its lifecycle in the following two cases.

10.2.3.1 Normal Destruction (Completion) — A CLJ object is destructed when the carrier is unloaded from the equipment.

10.2.3.2 Abnormal Destruction (Abortion) — A CLJ object is destructed when the CLJ is cancelled before receiving a carrier or aborted before unloading the carrier for some reasons such as an error.

10.2.4 CLJ Object Persistence — A CLJ Object may persist over equipment shut down to restart if the carriers still stay in the equipment. Capability to perform this persistence automatically is dependent on equipment design. In any case, when equipment moves into host control with a carrier on it, a CLJ which represents the carrier shall be created.

10.3 CLJ Object Functional Requirements

10.3.1 CLJ Main State Management — A function to manage the main state of CLJ. The CLJ main state represents the actual (nonpredictive) portion of the behavior.

<#4>

10.3.2 Predictions — A function to predict the requested start or end timing of Load Request or Unload Request state by equipment. Equipment may assert Prediction whenever the equipment can predict those timings.

10.3.2.1 Start of Load Request (SoLR) Prediction (Optional) — An optional function which predicts the timing at which Load Request state starts. This function is an option mainly for Internal Buffer Equipment. In normal cases, Fixed Buffer Equipment does not need to implement this function.

10.3.2.2 End of Load Stagnation Request (EoLSR) Prediction (Optional) — An optional function which predicts Load Stagnation timing by which the CLJ should be loaded with a carrier (Load Request state should be completed) and should move to Carrier Valid state for seamless cascading. An optional function which predicts a required timing of the beginning of Carrier Valid state at which Load Request state should be completed with carrier load. When the carrier is not loaded and valid by this predicted timing, stagnation of the carrier flow is likely to occur, and </#4> the stagnation of <#1> the equipment process related PEC </#1> may occur.

<#4>

10.3.2.3 Start of Unload Request (SoUR) Prediction — A function which predicts the start timing of Unload Request state, at which the equipment ends all work with the carrier and requests unload.

10.3.2.4 End of Unload Stagnation Request (EoUSR) Prediction (Optional) — An optional function which predicts Unload Stagnation timing by which the CLJ should be unloaded with the carrier (Unload Request state should be completed) and should be deleted for seamless cascading. When the carrier is not unloaded by this predicted timing, subsequent carrier load (or unload in internal buffer equipment) may be delayed and likely to cause the stagnation. An optional function which predicts the end timing of Unload Request state by which the equipment requires to finish the unloading.

</#4>

10.3.3 Carrier ID Assignment (Optional) — An optional function which manages the assignment of a carrier to the CLJ. In case neither check nor negotiation of the order of carrier handling is done through PCL functionalities, this option may not be required.

10.3.3.1 Late Carrier Assignment — A function to assign carrier after CLJ is created. This enables the use of Load Request function, in which equipment basically does not know which carrier will be assigned.


Doc. 5735 SEMI



Date: 5/7/23

10.3.3.2 Carrier Type (Optional) — An optional attribute to indicate which kind of carrier is dealt with the CLJ.

10.3.4 Load Port Assignment (optional) — An optional function which manages the assignment of a load port to the CLJ. A CLJ uses load port in order to perform physical handoff operation between AMHS at the last part of Load Request or Unload Request state.

10.3.4.1 Dynamic Load Port Assignment (optional) — An optional function which creates CLJ without load port assignment and assigns a load port when a coordination is done. This function is mainly for Internal Buffer Equipment. Since load ports in Internal Buffer Equipment are places which can temporarily be used for both Load and Unload, assignment of them should be done just before Load/Unload operation for more effective scheduling.

10.4 CLJ Object Attribute Definitions — The following table defines the attributes of CLJ object.

10.4.1 Who to maintain the Attributes — All attributes in the following table are always maintained and updated by the equipment.

10.4.2 Validity of Attributes of Parallel States — Attributes of parallel states are valid only when the parent state is active.

Table 21 CLJ Object Attribute Definition


ObjID CLJ object identifier. RO Y Text.CLJID. Numerical text expression of positive integer.ObjID is equipment defined.

ObjType Object Type. RO Y Text = ‘CarrierLogisticsJob’<#1>PECIDCarrierFlowID</#1>

Optional<#1>Identifier of PECIdentifier of carrier flowThis indicates in which carrier flow this CLJ belongs to.</#1>

RO <#2>Y O

</#2>

<#1>Positive Integer‘0’ indicates the case the CLJ is not associated to particular PEC yet.Unsigned Integer‘0’: Default carrier flow‘1’ or more: User defined carrier flow</#1>

CLJState The main state of CLJ State Model RO Y Enumerated:LoadQueued, LoadRequest, CarrierValid, UnloadRequest

SoLRPState OptionalCurrent state of SoLR Prediction parallel state

RO <#2>Y O

</#2>

Enumerated:SoLRNotPredicted, SoLRPredicted

SoLRPTime OptionalPredicted time of SoLR Prediction

RO <#2>Y O

</#2>

Uses format defined for TimeReport

EoLRPState OptionalCurrent state of EoLR Prediction parallel state

RO <#2>Y O

</#2>

Enumerated:EoLRNotPredicted, EoLRPredicted

EoLRPTime OptionalPredicted time of EoLR Prediction

RO <#2>Y O

</#2>


SoURPState Current state of SoUR Prediction parallel state

RO Y Enumerated:SoURNotPredicted, SoURPredicted

SoURPTime Predicted time of SoUR Prediction RO Y Uses format defined for TimeReport


Doc. 5735 SEMI



Date: 5/7/23


EoURPState OptionalCurrent state of EoUR Prediction parallel state

RO <#2>Y O

</#2>

Enumerated:EoURNotPredicted, EoURPredicted

EoURPTime OptionalPredicted time of EoUR Prediction

RO <#2>Y O

</#2>


CLJCarrierType OptionalType of carrier

RO <#2>Y O

</#2>

Enumerated:ProcessCarrier, EmptyCarrier, NPWCarrier

CLJCarrierID ID of carrier which is dealt with the CLJ. Carrier ID may not be assigned until a carrier is loaded and confirmed. When carrier ID is not specified yet, this attribute shall inform it.

RO Y Text 0–80 charactersIdentifier of a carrier. The CLJCarrierID shall be same as the CarrierID defined in SEMI E87.A zero length is used for ‘CarrierID is not yet specified’

CLJLPID Load port IDID of load port which will be used by the CLJ

RO Y Positive Unsigned integer.0 = Load port is not assignedNon 0 = Load port numberThe CLJLPID is compatible with the load port number defined in SEMI E87 which says “The load port number shall be assigned incrementally from the bottom left to bottom right, then top left to top right when facing the front of the equipment.”

#1 Even though a value may be marked as RO (read only), the initial value for the attribute may be provided by the host.

10.5 CLJ State Model — The following diagrams and tables define the state model of CLJ object. Equipment shall maintain appropriate number of CLJs to achieve continuous substrate processing.

10.5.1 CLJ State Model Diagram

<#4>Delete</#4>


Doc. 5735 SEMI



Date: 5/7/23


CLJ State Model Diagram


Doc. 5735 SEMI



Date: 5/7/23

10.5.2 CLJ State Model Definition

<#4>Table 22 CLJ State Model Definition

State Transition




New State

Comments

- - (No state) Tc00 New CLJ demand without load request

Create CLJCLJ Event

Sc01 Early creation of CLJ

Tc02 New CLJ demand with load request

Create CLJCLJ Event

Sc02 Normal creation

Tc04 New CLJ demand triggered by AMHS

Create CLJCLJ Event

Sc03 For Interim solution use only

Sc00 CLJ Created A CLJ is created and active.

Tc07 Any fatal error occurred. Delete CLJCLD Event

-(No state)

CLJ is aborted

Sc30 SoUR Predictable

Start of Unload Request is predictable

- - - - A state for parallel state definition

1Sc20 EoLR Predictable

End of Load Request is predictable


Sc10 SoLR Predictable

Start of Load Request is predictable


Sc01 Load Queued

The CLJ is queued in CFJ

Tc01 The CLJ requests load CLJ Event Sc02

Sc11 SoLR Prediction

Predictions of the start of Load Request

Tc10 None None Sc12 Parallel state of Sc10

Sc12 SoLR Not Predicted

Start tTiming of to SoLR is not predicted

Tc11 Prediction is done SoLR Event Sc13

Sc13 SoLR Predicted

Start tTiming of to SoLR is predicted

Tc12 Prediction is changed SoLR Event Sc13 Prediction updateTc13 Prediction is withdrawn SoLR Event Sc12

Sc02 Load Request

The CLJ is requesting load of a carrier

Tc03 A carrier is loaded CLJ Event Sc03

Sc21 EoLR Prediction

Predictions of the end of Load Request


Sc22 EoLR Not Predicted

Start tTiming of LS to EoLR is not predicted

Tc21 Prediction is done EoLR Event Sc23

Sc23 EoLR Predicted

Start tTiming of LS to EoLR is predicted

Tc22 Prediction is changed EoLR Event Sc23 Prediction updateTc23 Prediction is withdrawn EoLR Event Sc22

Sc03 Carrier Valid

The CLJ is loaded with a carrier

Tc05 The carrier is closed and ready for unload

CLJ Event Sc04

Sc31 SoUR Prediction

Predictions of the start of Unload Request


Sc32 SoUR Not Predicted

Start tTiming of to SoUR is not predicted

Tc31 Prediction is done. SoUR Event Sc33

Sc33 SoUR Predicted

Start tTiming of to SoUR is predicted

Tc32 Prediction is changed SoUR Event Sc33 Prediction updateTc33 Prediction is withdrawn SoUR Event Sc32

Sc04 Unload Request

The CLJ is requesting unload of a carrier

Tc06 The carrier is unloaded Delete CLJ CLD Event

-(No state)

CLJ is completed

Sc41 EoUR Prediction

Predictions of the end of Unload Request



Doc. 5735 SEMI



Date: 5/7/23

State Transition




New State

Comments

Sc42 EoUR Not Predicted

Start tTiming of US to EoUR is not predicted

Tc41 Prediction is done EoUR Event Sc43

Sc43 EoUR Predicted

Start tTiming of US to EoUR is predicted

Tc42 Prediction is changed EoUR Event Sc43 Prediction updateTc43 Prediction is withdrawn EoUR Event Sc42

Sc50 Load Port Assignment

Load Port assignment. Tc50 None None Sc51 Parallel state of Sc00

Sc51 LP Not Assigned

CLJ is not assigned on load port

Tc51 Load port assignment LP Event Sc52

Sc52 LP Assigned CLJ is assigned on load port

Tc52 Load port re-assignment LP Event Sc52Tc53 Load port assignment

withdrawalLP Event Sc51

Sc60 Carrier ID Assignment

Carrier ID assignment. Tc60 None None Sc61 Parallel state of Sc00

Sc61 CID Not Assigned

Carrier ID is not assigned

Tc61 Carrier ID assignment CID Event Sc62

Sc62 CID Assigned

Carrier ID is assigned Tc62 Carrier ID reassignment CID Event Sc62Tc63 Carrier ID withdrawal CID Event Sc61

</#4>#1 Numeric portion of the transition numbers in this column shall be used as event numbers.#2 Events in the Action column report the following information. CLJ Event reports CLJID and CLJState CLD Event reports CLJID and previous CLJState SoLR Event reports CLJID, SoLRPState and SoLRPTime EoLR Event reports CLJID, EoLRPState and EoLRPTime SoUR Event reports CLJID, SoURPState and SoURPTime EoUR Event reports CLJID, EoURPState and EoURPTime CID Event reports CLJID, CLJCarrierType and CLJCarrierID LP Event reports CLJID and CLJLPID

10.5.3 CLJ State Definition Table

<#4>Table 23 State Definition Table


Sc00 CLJ Created A state in which a CLJ is created and in operation.Sc01 Load Queued Optional

The CLJ is queued in CFJ, but is not requesting load of a carrier yet.This state may not be required when SoLR Load Request Prediction is not used.


Doc. 5735 SEMI



Date: 5/7/23


Sc02 Load Request The CLJ is requesting load of a carrier.This state may not be required when EoLR Load Stagnation Prediction is not used.This state is not equal to ready to load. Logical readiness to load is determined by the position of the CLJ in CFJ. Physical readiness to load shall be confirmed by using SEMI E87 functionalities.Fixed Buffer Equipment: In normal cases, the CLJ is assigned on a load port.Internal Buffer Equipment: The CLJ may or may not be assigned on a load port at the beginning of this state.Multiple CLJs may be in Load Request state considering a dynamic use of multiple load ports for multiple CLJs in AMHS arrival order. The arbitration algorithm is not defined in this Standard.

Sc03 Carrier Valid The CLJ is loaded with a carrier.The carrier is waiting for the use or in use, and is valid for the equipment.This state starts with the end of SEMI E84 sequence for load, and ends when the use of the carrier at FIMS port (Load port for Fixed Buffer Equipment, internal FIMS port for Internal Buffer Equipment) is completed, the door is closed, undocked or ready to undock, and the equipment has no operation other than unload.

Sc04 Unload Request The CLJ is requesting unload of the carrier assigned to the CLJ.This state is not equal to ready to unload. Logical readiness to unload is determined by the priority of the CLJ in CFJ. Physical readiness to unload shall be confirmed by using SEMI E87 functionalities.Fixed Buffer Equipment: In normal cases, the CLJ stays assigned on the same load port.Internal Buffer Equipment: The CLJ may not be assigned on a load port at the beginning of this state when arbitration of load ports to CLJs is done by the arrival order information from AMHS.

Sc10 SoLR Predictable A super state of Load Queued stateThis state has SoLR Predictable parallel state.In this state, SoLR Prediction function is active.

Sc11 SoLR Prediction An optional parallel state of SoLR Predictable stateThis state represents the status of Start of Load Request Prediction.

Sc12 SoLR Not Predicted The start timing of Load Request state to SoLR is not predicted.Sc13 SoLR Predicted The start timing of Load Request state to SoLR is predicted.Sc20 EoLR Predictable A super state of Load Queued and Load Request states

This state has EoLR Predictable parallel state.In this state, EoLR Prediction function is active.

Sc21 EoLR Prediction An optional parallel state of EoLR Predictable stateThis state represents the status of End of Load Request Prediction.

Sc22 EoLR Not Predicted The start timing of Load Stagnation to EoLR is not predicted.Sc23 EoLR Predicted The start timing of Load Stagnation to EoLR is predicted.Sc30 SoUR Predictable A super state of Load Queued, Load Request, and Carrier Valid states

This state has SoUR Predictable parallel state.In this state, SoUR Prediction function is active.

Sc31 SoUR Prediction A parallel state of SoUR Predictable stateThis state represents the status of Start of Unload Request Prediction.

Sc32 SoUR Not Predicted The start timing of Unload Request state to SoUR is not predicted.Sc33 SoUR Predicted The start timing of Unload Request state to SoUR is predicted.


Doc. 5735 SEMI



Date: 5/7/23


Sc41 EoUR Prediction An optional parallel state of CLJ Created stateThis state represents the status of End of Unload Request Prediction.

Sc42 EoUR Not Predicted The start timing of Unload Stagnation to EoUR is not predicted.Sc43 EoUR Predicted The start timing of Unload Stagnation to EoUR is predicted.Sc50 Load Port

AssignmentAn optional parallel state of CLJ CreatedThis state represents the status of Load Port Assignment.

Sc51 LP Not Assigned The CLJ is not assigned on load port yet.Sc52 LP Assigned The CLJ is assigned on load port.Sc60 Carrier ID

AssignmentAn optional parallel state of CLJ CreatedThis state represents the status of Carrier ID Assignment.

Sc61 CID Not Assigned Carrier ID (CLJCarrierID) is not assigned to the CLJ yet.Sc62 CID Assigned Carrier ID (CLJCarrierID) is assigned to the CLJ.

</#4>

10.5.4 CLJ State Transition Table

<#4>Table 24 CLJ State Transition Table


Tc00 (No state) New Carrier Logistics demand occurred. Load Queued Create CLJCLJ Event

Early creation of CLJ

Tc01 Load Queued Request loading of a carrier. Load Request CLJ EventTc02 (No state) New Carrier Logistics demand occurred

and is requesting load of a carrier.Load Request Create CLJ

CLJ EventNormal creation of CLJ

Tc03 Load Request A carrier is loaded and SEMI E84 sequence is completed.

Carrier Valid CLJ Event Factory level timing which indicates that the carrier is under control of equipment

Tc04 (No state) New Carrier Logistics demand occurred by arrival of AMHS while no CLJ is assigned on the load port.

Carrier Valid Create CLJCLJ Event

For Interim solution only

Tc05 Carrier Valid The carrier is ready to unload. Carrier door shall be closed and undocked before this transition. In case the load port has a purge capability, it shall also be done before this transition.

Unload Request

CLJ Event Load port may not be assigned yet

Tc06 Unload Request The carrier is unloaded. (No state) Delete CLJCLD Event

Normal completion

Tc07 CLJ Created Any fatal error. (No state) Delete CLJCLD EventError report

Abnormal end

Tc10 SoLR Prediction

None. SoLR Not Predicted

None

Tc11 SoLR Not Predicted

Start timing of Load Request state Time of SoLR is predicted.

SoLR Predicted

SoLR Event

Tc12 SoLR Predicted Predicted start timing of Load Request state time of SoLR is changed.

SoLR Predicted

SoLR Event


Doc. 5735 SEMI



Date: 5/7/23


Tc13 SoLR Predicted Predicted start timing of Load Request state time of SoLR is withdrawn.

SoLR Not Predicted

SoLR Event

Tc20 EoLR Prediction

None EoLR Not Predicted

None

Tc21 EoLR Not Predicted

Start timing of Load Stagnation Time of EoLR is predicted.

EoLR Predicted

EoLR Event

Tc22 EoLR Predicted Predicted start timing of Load Stagnation time of EoLR is changed.

EoLR Predicted

EoLR Event

Tc23 EoLR Predicted Predicted start timing of Load Stagnation time of EoLR is withdrawn.

EoLR Not Predicted

EoLR Event

Tc30 SoUR Prediction

None SoUR Not Predicted

None

Tc31 SoUR Not Predicted

Start timing of Unload Request state Time of SoUR is predicted.

SoUR Predicted

SoUR Event

Tc32 SoUR Predicted Predicted start timing of Unload Request state time of SoUR is changed.

SoUR Predicted

SoUR Event

Tc33 SoUR Predicted Predicted start timing of Unload Request state time of SoUR is withdrawn.

SoUR Not Predicted

SoUR Event

Tc40 EoUR Assignment

None EoUR Not Predicted

None

Tc41 EoUR Not Predicted

Start timing of Unload Stagnation Time of EoUR is predicted.

EoUR Predicted

EoUR Event

Tc42 EoUR Predicted Predicted start timing of Unload Stagnation time of EoUR is changed.

EoUR Predicted

EoUR Event

Tc43 EoUR Predicted Predicted start timing of Unload Stagnation time of EoUR is withdrawn.

EoUR Not Predicted

ESoUR Event

Tc50 Load Port Assignment

None. LP Not Assigned

None

Tc51 LP Not Assigned

CLJ is assigned on load port. LP Assigned LP Event

Tc52 LP Assigned CLJ is re-assigned on load port. LP Assigned LP EventTc53 LP Assigned Load port assignment withdrawal. LP Not

AssignedLP Event

Tc60 Carrier ID Assignment

None. CID Not Assigned

None

Tc61 CID Not Assigned

Carrier ID assignment. CID Assigned CID Event

Tc62 CID Assigned Carrier ID reassignment. CID Assigned CID EventTc63 CID Assigned Carrier ID withdrawal. CID Not

AssignedCID Event

</#4>

#1 Numeric portion of the transition numbers in this column shall be used as event numbers.#2 Events in the Action column report the following information.


Doc. 5735 SEMI



Date: 5/7/23

CLJ Event reports CLJID and CLJState CLD Event reports CLJID and previous CLJState SoLR Event reports CLJID, SoLRPState and SoLRPTime EoLR Event reports CLJID, EoLRPState and EoLRPTime SoUR Event reports CLJID, SoURPState and SoURPTime EoUR Event reports CLJID, EoURPState and EoURPTime CID Event reports CLJID, CLJCarrierType and CLJCarrierID LP Event reports CLJID and CLJLPID

10.6 CLJ Services — This section defines the message services required to support CLJ functionalities.

10.6.1 CLJ Service Message Description — The following table is a list of CLJ services.

Table 25 CLJ Service Message Description


GetCLJList R OptionalThis service gets a list of the CLJ objects from the equipment.Use SEMI E39 OSS to get ObjIDList by specifying ObjType and ObjID for ATTRID.

GetCLJAttributes R OptionalThis service gets the attributes of specified CLJ from the equipment.Use GetAttr service of SEMI E39 OSS for this purpose.

#1 The ‘Type’ column is used to indicate whether the service consists of a request/response message pair, ‘R’, or a single notification message, ‘N’.

10.7 CLJ Variable Data Definitions — This section defines variable data requirements for CLJ compliant equipment. Values of these variables are available to the host via collection event reports and host status queries.

Table 26 CLJ Variable Data Definitions


CLJID ObjID of CLJCLJID is equipment defined

Numerical text expression of positive integer

RO

<#1>PECIDCarrierFlowID</#1>

Optional<#1>Identifier of PECIdentifier of carrier flowThis indicates in which carrier flow this CLJ belongs to.</#1>

<#1>Positive Integer‘0’ indicates the case the CLJ is not associated to particular PEC yet.Unsigned Integer‘0’: Default carrier flow‘1’ or more: User defined carrier flow</#1>

RO

CLJState The main state of CLJ State Model Enumerated:LoadQueued, LoadRequest, CarrierValid, UnloadRequest

RO

SoLRPState OptionalCurrent state of SoLR Prediction parallel state

Enumerated:SoLRNotPredicted, SoLRPredicted

RO

SoLRPTime OptionalPredicted time of SoLR Prediction


RO


Doc. 5735 SEMI



Date: 5/7/23


EoLRPState OptionalCurrent state of EoLR Prediction parallel state

Enumerated:EoLRNotPredicted, EoLRPredicted

RO

EoLRPTime OptionalPredicted time of EoLR Prediction


RO

SoURPState Current state of SoUR Prediction parallel state

Enumerated:SoURNotPredicted, SoURPredicted

RO

SoURPTime Predicted time of SoUR Prediction Uses format defined for TimeReport

RO

EoURPState OptionalCurrent state of EoUR Prediction parallel state

Enumerated:EoURNotPredicted, EoURPredicted

RO

EoURPTime OptionalPredicted time of EoUR Prediction


RO

CLJCarrierType OptionalType of carrier

Enumerated:ProcessCarrier, EmptyCarrier, NPWCarrier

RO

CLJCarrierID OptionalID of carrier which is dealt with the CLJ. Carrier ID may not be assigned until a carrier is loaded and confirmed. In case carrier ID is not specified yet, this variable shall inform it.

Text 0–80 charactersIdentifier of a carrier. The CLJCarrierID shall be same as the CarrierID defined in SEMI E87.A zero length is used for ‘CarrierID is not yet specified’

RO

CLJLPID OptionalLoad port IDID of load port which will be used by the CLJ

Positive Unsigned integer0 = Load port is not assignedNon 0 = Load port numberThe CLJLPID is compatible with the load port number defined in SEMI E87 which says “The load port number shall be assigned incrementally from the bottom left to bottom right, then top left to top right when facing the front of the equipment.”

RO

11 Requirements for Compliance11.1 Following table provides a checklist for PCL compliance.

Table 27 PCL Compliance Statement

Fundamental PCL Requirements PCL Section Implemented PCL Compliant

PCL Requirements 8PCL Requirements 8.1

Carrier Flow Job (CFJ) Object 8.1.1 Yes NoCarrier Logistics Job (CLJ) Object 8.1.2 Yes No

Reporting Scheme of Time for PCL 8.2 Yes No


Doc. 5735 SEMI



Date: 5/7/23

Fundamental PCL Requirements PCL Section Implemented PCL Compliant

Prediction Resubmission Threshold for PCL 8.3 Yes NoPCL Value Data Definitions 8.4 Yes NoTimeReport 8.5 Yes No

CFJ Object Requirements 9CFJ Object Definition 9.1 Yes NoCFJ Object Descriptions 9.2 Yes NoCFJ Object Functional Requirements 9.3

Order Management of CLJs 9.3.1 Yes NoLoad/Unload Timing Management of CLJs 9.3.2 Yes NoLoad Port Assignment to CLJs 9.3.3

Load Port Assignment for Fixed Buffer Equipment 9.3.3.1 Yes NoLoad Port Assignment for Internal Buffer Equipment 9.3.3.2 Yes No

CFJ Attribute Definitions 9.4 Yes NoCFJ State Model 9.5 Yes NoCFJ Services 9.6 Yes NoCFJ Variable Data Definitions 9.7 Yes No

CLJ Object Requirements 10CLJ Object Definition 10.1 Yes NoCLJ Object Description 10.2 Yes NoCLJ Object Functional Requirements 10.3

CLJ Main State Management 10.3.1 Yes NoPredictions 10.3.2

<#4>Start of Load Request (SoLR) Prediction (Optional)</#4>

10.3.2.1 Yes No

<#4>End of Load Stagnation Request (EoLSR) Prediction (Optional)</#4>

10.3.2.2 Yes No

<#4>Start of Unload Request (SoUR) Prediction</#4>

10.3.2.3 Yes No

<#4>Endo of Unload Stagnation Request (EoUSR) Prediction (Optional)</#4>

10.3.2.4 Yes No

Carrier ID Assignment (Optional) 10.3.3 Yes NoLoad Port Assignment (Optional) 10.3.4 Yes No

CLJ Object Attribute Definitions 10.4 Yes NoCLJ State Model 10.5 Yes NoCLJ Services 10.6 Yes NoCLJ Variable Date Definitions 10.7 Yes No


Doc. 5735 SEMI



Date: 5/7/23

12 Related Documents12.1 SEMI Standards and Safety Guidelines

SEMI E148 — Specification for Time Synchronization and Definition of the TS-CLOCK Object


Doc. 5735 SEMI



Date: 5/7/23

APPENDIX 1APPLICATION EXAMPLES FOR SIMPLE FIXED BUFFER EQUIPMENTNOTICE: The material in this Appendix is an official part of SEMI E171 and was approved by full letter ballot procedures on August 25, 2014.

A1-1 Implementations for Simple Fixed Buffer EquipmentA1-1.1 Purpose — The purpose of this Appendix is to show how the optional functionalities are used for simple Fixed Buffer Equipment.

A1-1.2 Configuration of the Equipment — This implementation example uses following configuration.

Number of Load Ports — Two (Alternative use)

<#1>

Number of carrier flows PECs — One (CarrierFlowID is not used Single thread of process).

</#1>

A1-2 Interim Implementation for Simple Fixed Buffer EquipmentA1-2.1 Purpose of Interim Implementation — The purpose of this implementation is to provide SoUR prediction capability with minimal implementation effort. <#3> For simplicity, CLJs are managed per load port basis. And, each load port has up to one CLJ. </#3> This implementation is easily extendable to LP-Based implementation.

A1-2.2 Relationship Model of Objects — The CFJ and CLJ relationship for simple Fixed Buffer Equipment is shown below.

Number of CFJs — One CFJ is assigned to each load port (two CFJs are used)

Number of CLJs — Up to one CLJ is created per load port (= per CFJ)

Maximum Number of Carriers (MaxCarrierNumber) — One (for one load port)

Load Port Assignment — Not used

Carrier ID Assignment — Not used

SoLR Prediction — Not used

EoLR Prediction — Not used

SoUR Prediction — Used

EoUR Prediction — Not used


Doc. 5735 SEMI



Date: 5/7/23

<#1>Delete</#1>

<#1>Add</#1>Figure A1-1

CFJ and CLJ Relationship for Interim Implementation for Simple Fixed Buffer Equipment

A1-2.3 CLJ State Model — The CLJ uses the following portions of the CLJ State Model.


Doc. 5735 SEMI



Date: 5/7/23

<#4>Delete</#4>


CLJ State Model for Interim Implementation for Simple Fixed Buffer Equipment<#3>

A1-2.4 CFJ for Interim Implementation for One Load Port of Simple Fixed Buffer Equipment — In this implementation, CFJ is assigned to each load port. Each CFJ which is assigned to each load port has the following configuration. Each CFJ has up to one CLJ because the CLJ does not have Load Queued state or Load Request state in this implementation.

2: The following figure only shows the highlighted attributes of CLJ.

</#3>


Doc. 5735 SEMI



Date: 5/7/23

Figure A1-1CFJ for Interim Implementation for Simple Fixed Buffer Equipment

A1-3 LP-Based Implementation for Simple Fixed Buffer Equipment<#3>

A1-3.1 Purpose of LP-Based Implementation — The purpose of LP-Based implementation is to provide EoLR Prediction and SoUR Prediction capabilities with minimum implementation effort. For simplicity, CLJs are managed per load port basis. And, each load port has up to two CLJs, that are and only current and the next (predicted) for each load port. So, flexible assignment of load port to CLJ is not covered.

</#3>

A1-3.2 Relationship Model of Objects — The CFJ and CLJ relationship for simple Fixed Buffer Equipment is shown below.

Number of CFJs — One CFJ is assigned to each load port (two CFJs are used)

Number of CLJs — Up to two CLJs are created per load port (= per CFJ)

Maximum Number of Carriers (MaxCarrierNumber) — One (for one load port)

Load Port Assignment — Not used

Carrier ID Assignment — Not used


EoLR Prediction — Used




Doc. 5735 SEMI



Date: 5/7/23

<#1>Delete</#1>


CFJ and CLJ Relationship for LP-Based Implementation for Simple Fixed Buffer Equipment

A1-3.3 CLJ State Model — The CLJ uses the following portion of the CLJ State Model.


Doc. 5735 SEMI



Date: 5/7/23

<#4>Delete</#4>


CLJ State Model for LP-Based Implementation for Simple Fixed Buffer Equipment

A1-3.4 CFJ for One Load Port of Simple Fixed Buffer Equipment — Each CFJ which is assigned to each load port has the following configuration.

<#3>

3: The following figure only shows the highlighted attributes of CLJs.

</#3>


Doc. 5735 SEMI



Date: 5/7/23

Figure A1-1CFJ for LP-Based Implementation for Simple Fixed Buffer Equipment

A1-4 Basic Implementation for Simple Fixed Buffer EquipmentA1-4.1 Relationship Model of Objects — The CFJ and CLJ relationship for simple Fixed Buffer Equipment is shown below.

Number of CFJs — One CFJ is assigned to whole equipment (one CFJ manages two load ports)

Number of CLJs — Up to four CLJs are created

Maximum Number of Carriers (MaxCarrierNumber) — Two (one for one load port)

Load Port Assignment — Used

Carrier ID Assignment — Used






Doc. 5735 SEMI



Date: 5/7/23

<#1>Delete</#1>


CFJ and CLJ Relationship for Basic Implementation for Simple Fixed Buffer Equipment



Doc. 5735 SEMI



Date: 5/7/23

<#4>Delete</#4>


CLJ State Model for Basic Implementation for Simple Fixed Buffer Equipment

A1-4.3 CFJ for Simple Fixed Buffer Equipment — CFJ which is assigned to the equipment has the following configuration.

<#3>


</#3>


Doc. 5735 SEMI



Date: 5/7/23

Figure A1-1CFJ for Basic Implementation for Simple Fixed Buffer Equipment

A1-4.4 Transaction and States of Basic Implementation for Simple Fixed Buffer Equipment — Transactions and states are shown in the following table.

<#3>Table A1-1 Transactions and States

# Action Dir#1 Message & Event

E87#2 LPTS PCL#3 PJ/CJ

LP1 LP2 CLJ1 CLJID =0001

CLJ2 CLJID =0002

CLJ3 CLJID =0003

CLJ4 CLJID =0004

Job1 (CLJ1,3)

Job2 (CLJ2,4)

1 Initial State RL RL None None None None None None2 CLJ1,CLJ2

Created &Load Request

FE CLJ Event LR LR

3 CLJ1,CLJ2 EoLR Predicted

FE EoLR Event Time = Now

EoLR Predicted

EoLR Predicted

4 F E Start of E84 TB5 CLJ1

Carrier Valid (Loaded)

FE CLJ Event(@ End of E84)

CV

6 CLJ1 Slot Map VerificationPJ Creation

Created/Execute

7 CLJ1SoUR Predicted

FE SoUR Event Time = T1

SoUR Predicted

8 F E Start of E84 TB


Doc. 5735 SEMI



Date: 5/7/23




CLJ2 CLJID =0002

CLJ3 CLJID =0003

CLJ4 CLJID =0004

Job1 (CLJ1,3)

Job2 (CLJ2,4)

9 CLJ2Carrier Valid (Loaded)


CV


Created/Execute



SoUR Predicted

12 CLJ3Load Request

FE CLJ Event LR

13 CLJ3EoLR Predicted

FE EoLR Event Time = T3

(CEW Started)

EoLR Predicted

14 CLJ1Unload Request

FE CLJ Event RU UR

15 F E Start of E84 TB16 CLJ1 Deleted

(Unloaded)FE CLJ Event

(@End of E84)RL Deleted Deleted

17 F E Start of E84 TB None None18 CLJ3



CV


Created/Execute



SoUR Predicted

21 CLJ4Load Request

FE CLJ Event LR

22 CLJ4EoLR Predicted

FE EoLR Event Time = T5

(CEW Started)

EoLR Predicted


FE CLJ Event RU UR



(@ End of E84)RL Deleted Deleted

26 F E Start of E84 TB None None27 CLJ4



CV


Created/Execute


Doc. 5735 SEMI



Date: 5/7/23




CLJ2 CLJID =0002

CLJ3 CLJID =0003

CLJ4 CLJID =0004

Job1 (CLJ1,3)

Job2 (CLJ2,4)



SoUR Predicted


FE CLJ Event RU UR





FE CLJ Event RU None UR None




#1 F = Factory system, E = Equipment.#2 LPTS = Load Port Transfer State, RL = Ready to Load, TB = Transfer Blocked, RU = Ready to Unload.#3 LR = Load Request, CV = Carrier Valid, UR = Unload Request.

</#3>


Doc. 5735 SEMI



Date: 5/7/23

APPENDIX 2APPLICATION EXAMPLES FOR INTERNAL BUFFER EQUIPMENTNOTICE: The material in this Appendix is an official part of SEMI E171 and was approved by full letter ballot procedures on August 25, 2014.

A2-1 Implementation for Internal Buffer EquipmentA2-1.1 Purpose — The purpose of this Appendix is to show how the optional functionalities are used for Internal Buffer Equipment.

A2-1.2 Configuration of the Equipment — This implementation example uses following configuration.

Number of Load Ports — Two. Independently usable for both load and unload.

<#1>

Number of carrier flows PECs — One (CarrierFlowID is not used). One batch can be processed at a time.

</#1>

<#3>

Number of Carriers for One Batch — Two Four. Two Four carriers of wafers for one batch.

Number of Internal Buffers for Carriers for Production — Four Eight. Carriers up to two batches can be stored.

A2-2 Bi-Direction Implementation for Internal Buffer EquipmentA2-2.1 Relationship Model of Objects — The CFJ and CLJ relationship for Internal Buffer Equipment is shown below.

Number of CFJs — One. For flexible use of load port.

Number of CLJs — Up to six 12 CLJs. Two Four CLJs for the wafers in process, two four CLJs for the wafers being unloaded, and two four CLJs for the wafers to be loaded.

Maximum Number of Carriers (MaxCarrierNumber) — Four Eight

Load Port Assignment — Used

Carrier ID Assignment — Used





</#3>


Doc. 5735 SEMI



Date: 5/7/23

<#1>Delete</#1>


CFJ and CLJ Relationship for Bi-Direction Implementation for Internal Buffer Equipment



Doc. 5735 SEMI



Date: 5/7/23

<#4>Delete</#4>


CLJ State Model for Bi-Direction Implementation for Internal Buffer Equipment<#3>

A2-2.3 CFJ for Internal Buffer Equipment — CFJ has the following configuration. CFJ has six 12 CLJs at maximum; two four are for the carriers in process, two four are carriers for being unloaded, and two four are for carriers to be loaded.

A2-2.3.1 The First Table — The first table in the following figure shows the timing at which the Predictions for Batch 2 are just done. At this timing, Unload Request Predictions of CLJs for Batch 0 are already done and those CLJs are about to move to Unload Request state. On the other hand, the carriers for Batch 1 (C4 through C7) are loaded and are in Carrier Valid state, and Unload Request Prediction is done. This enables the equipment to predict the timing by which the equipment needs to have the carriers for Batch 2. The first table shows the timing at which batch A is becoming unload request and batch B is now in process. The wafers for CLJID=0001 are already unloaded from process unit to carrier C0 and the carrier is in Unload Request state. The wafers for CLJID=0002 are being unloaded to carrier C1 and the carrier is predicted to be Unload Requested state at hh.mm.ss1. CLJID=0005,


Doc. 5735 SEMI



Date: 5/7/23

0006 are in Load Request state and are predicted (requested) to be finished by hh.mm.ss2, hh.mm.ss3. CLJID=0001 and CLJID=0005 share the same CEW on load port 1 and should be completed by hh.mm.ss2.

A2-2.3.2 The Second Table — The second table shows the timing at which CLJ 00 and CLJ 01 are deleted as the carriers for them are already unloaded and CLJ 02 and CLJ 03 are in Unload Request state. As CLJ 00 and CLJ 01 are deleted, the resources to make CLJ 08 and CLJ 09 Load Request state are ready. The second table shows the timing at which CLJID=0001 is already deleted as C0 is unloaded, and CLJID=0002 is in Unload Request state. Carrier C4 for CLJID=0005 is already loaded, and CLJID=0006 is in Load Request state.

A2-2.3.3 The Third Table — The third table shows the timing at which all CLJs for Batch 0 are deleted as the carriers for them are unloaded and CLJ 08 and CLJ 09 become Carrier Valid state as the carriers for them are loaded. As CLJ 02 and CLJ 03 are deleted, the resources to make CLJ 10 and CLJ 11 Load Request state are ready. The third table shows the timing at which the batch B is about to end, and batch C is ready to process. CLJID=0007, 0008 are in Load Request state for cascading.



CFJ for Bi-Direction Implementation for Internal Buffer Equipment (Load Queued State is Used)

A2-2.3.4 Simplification — In this implementation, Load Queue state may be replaced with Load Request state for simplification because the host can understand the resource availability of the equipment as the MaxCarrierNumber is set to eight.



Doc. 5735 SEMI



Date: 5/7/23

<#3>Delete</#3>


CFJ for Bi-Direction Implementation for Internal Buffer Equipment (Load Queued State is not Used)</#3>

<#6>


Doc. 5735 SEMI



Date: 5/7/23

A2-2.4 Transaction and States of Bi-Direction Implementation for Internal Buffer Equipment — Transactions and states are shown in the following table.

Table A2-1 Transactions and States

# Action #1 Dir #2 Message & Event

E87 #3

LPTSPCL #4 PJ

/CJ #5

LP1

LP2

CLJ1 /13

CLJ2 /14

CLJ3 /15

CLJ4 /16

CLJ5

CLJ6

CLJ7

CLJ8

CLJ9

CLJ10

CLJ11

CLJ12

Job1Job2

1 Initial State RL RL N N N N N N N N N N N N N N2 CLJ1~12

Created & CLJ1 ~ 8 Load Request

F E CLJ Event LR LR LR LR LR LR LR LR

3 CLJ1~8 EoLR Predicted

F E EoLR Event Time CLJ1~4=

Now

LSP LSP LSP LSP

4 F E Start of E84 TB5 CLJ1 Carrier

Valid (Loaded)F E 　 CLJ Event

(@ End of E84)CV

6 CLJ1 Recognition of Carrier and Wafer

　　

7 CLJ1 Carrier Move to IB

　　 RL

8 　 F E Start of E84 TB

9 CLJ2 Carrier Valid (Loaded)

F E CLJ Event (@ End of E84)

CV


　　


　　 RL




CV


　　


　　 R L




CV


　　


　　 RL


Doc. 5735 SEMI



Date: 5/7/23


E87 #3

LPTSPCL #4 PJ

/CJ #5

LP1

LP2

CLJ1 /13

CLJ2 /14

CLJ3 /15

CLJ4 /16

CLJ5

CLJ6

CLJ7

CLJ8

CLJ9

CLJ10

CLJ11

CLJ12

Job1Job2

20 PJ Creation 　　21 CLJ1~4 SoUR

PredictedF E 　 SoUR Event

Time = T2URP URP URP URP C/

E22 CLJ5~8 EoLR

PredictedF E EoLR Event

Time CLJ5~8 =T1

LSP LSP LSP LSP




CV


　　


　　 RL




CV


　　


　　 RL




CV


　　


　　 RL




CV


　　


　　 RL

39 PJ Completed (Job1)

　　 D

40 PJ Creation (Job2)

　　 N C/E

41 CLJ9~12 Load Queued

　　 LQ LQ LQ LQ


F E EoLR Event Time = T5

LSP LSP LSP LSP


Doc. 5735 SEMI



Date: 5/7/23


E87 #3

LPTSPCL #4 PJ

/CJ #5

LP1

LP2

CLJ1 /13

CLJ2 /14

CLJ3 /15

CLJ4 /16

CLJ5

CLJ6

CLJ7

CLJ8

CLJ9

CLJ10

CLJ11

CLJ12

Job1Job2

43 CLJ5~8SoUR Predicted

F E SoUR Event Time = T6

URP URP URP URP

44 CLJ1 Unload Request

F E CLJ Event RU UR


F E CLJ Event RU UR


47 CLJ1 Deleted (Unloaded)

　　 RL D LR

48 CLJ9 Load Request

F E CLJ Event N


F E CLJ Event RU UR



　　 RL D LR


F E CLJ Event N


F E CLJ Event RU UR



　　 RL D LR


F E CLJ Event N



　　 RL D LR


F E CLJ Event N

60 　 F E Start of E84 TB CV




　　


　　 RL





　　


　　 RL

68 F E Start of E84 TB CV


Doc. 5735 SEMI



Date: 5/7/23


E87 #3

LPTSPCL #4 PJ

/CJ #5

LP1

LP2

CLJ1 /13

CLJ2 /14

CLJ3 /15

CLJ4 /16

CLJ5

CLJ6

CLJ7

CLJ8

CLJ9

CLJ10

CLJ11

CLJ12

Job1Job2


F E CLJ Event(@ End of E84)


　　


　　 RL

72 　 F E 　 Start of E84 TB CV

73 CLJ13~16 Load Queued

　　




　　


　　 RL

77 PJ Completed 　　 D

78 PJ Creation 　　 LQ LQ LQ LQ C/E

N


F E EoLR EventTime = T9

LSP LSP LSP LSP

80 CLJ9~12SoUR Predicted

F E SoUR Event Time = T10

URP URP URP URP


F E CLJ Event RU UR


F E CLJ Event RU UR



　　 RL D


F E CLJ Event LR N


F E CLJ Event RU UR

87 　 F E 　 Start of E84 TB


　 RL D


F E CLJ Event LR N


F E CLJ Event RU UR



　　 RL D


F E CLJ Event LR N



Doc. 5735 SEMI



Date: 5/7/23


E87 #3

LPTSPCL #4 PJ

/CJ #5

LP1

LP2

CLJ1 /13

CLJ2 /14

CLJ3 /15

CLJ4 /16

CLJ5

CLJ6

CLJ7

CLJ8

CLJ9

CLJ10

CLJ11

CLJ12

Job1Job2


　　 RL D


F E CLJ Event LR N





　　

100CLJ13 Carrier Move to IB

　　 RL

101　 F E Start of E84 TB CV

102CLJ14 Carrier Valid (Loaded)


103CLJ14 Recognition of Carrier and Wafer

　　


　　 RL

105　 F E Start of E84 TB



CV

107CLJ15 Recognition of Carrier and Wafer

　　


　　 RL

109　 F E Start of E84 TB


　F E

CLJ Event(@ End of E84)

CV

#1 IB = Internal Buffer #2 F = Factory system, E = Equipment #3 LPTS = Load Port Transfer State, RL = Ready to Load, TB = Transfer Blocked, RU = Ready to Unload #4 N = None, LR = Load Request, CV = Carrier Valid, UR = Unload Request, LQ = Load Queued, LSP = EoLR Predicted, URP = SoUR Predicted, D = Deleted#5 Job1 = Boat 1 for CLJ1-4, CLJ9-12, Job2 = Boat2 for CLJ5-8, CLJ13-16, N = None, C = Created, E = Execute, D = Deleted

</#6>


Doc. 5735 SEMI



Date: 5/7/23

NOTICE: SEMI makes no warranties or representations as to the suitability of the Standards and Safety Guidelines set forth herein for any particular application. The determination of the suitability of the Standard or Safety Guideline is solely the responsibility of the user. Users are cautioned to refer to manufacturer’s instructions, product labels, product data sheets, and other relevant literature, respecting any materials or equipment mentioned herein. Standards and Safety Guidelines are subject to change without notice.

By publication of this Standard or Safety Guideline, SEMI takes no position respecting the validity of any patent rights or copyrights asserted in connection with any items mentioned in this Standard or Safety Guideline. Users of this Standard or Safety Guideline are expressly advised that determination of any such patent rights or copyrights and the risk of infringement of such rights are entirely their own responsibility.


Doc. 5735 SEMI
