semi合集-English.pdf - 第1696页

SEMI E40-0705 © SEMI 1995, 2005 8 Sequence Erma SS AA Sequence S t ep (SS) AB SS AC PR BA Process Recipe (PR) BB PR BC PS CA Process Step (PS) CB PS CC PP DA Process Param ete r (PP) DB PP DC Figure 1 Cluster Tool Sequen…

100%1 / 7923
SEMI E40-0705 © SEMI 1995, 2005 7
7.4.1 The process job includes a processing descrip-tion (a recipe or process program) identifier that shall be unique
within the domain of the processing agent. The type and content of the processing description must be appropriate
for the processing resource and the type of material.
7.4.2 Creation and management of recipes and process programs is outside the scope of this standard.
7.5 Process Tuning — Feedforward and feedback control between process steps is becoming increasingly important
for process tuning in stabilizing processes, such as those which lack in-situ metrology, and demand increasing yields
(or performance). The process tuning requirements differ considerably with application, and there is little consensus
on any particular method. It is not the intention of this standard to provide compre-hensive support for process
tuning, but rather to provide a simple mechanism which may be extended. Support for recipe tuning is not a
fundamental requirement.
7.5.1 Processing management provides a mechanism for specification of the type of recipe method to be applied.
Two methods are defined in the standard: RecipeID only, and RecipeID and Variables. User-defined methods may
also be used, requiring all com-municating entities to have a common understanding of the particular definition and
application requirements.
7.5.2 The RecipeID only method accepts the identifier of the recipe to be applied but no additional tuning
parameters. The application recipe body is not precluded from defining any application tuning, but there is no
standardized support.
7.5.3 The RecipeID and Variables method provides a simple process tuning mechanism at process job creation to
support limited run to run feedforward and feedback control. It defines the VariableTuning method, which supplies a
list of variable names and values in the process job create. This sets variables defined in the recipe. Each variable
name shall be one of the exposed variable definitions supported in recipe management, and its value shall fall within
the range specified in the variable definition.
7.5.4 Recipe parameter names (RecipeVarName) shall be specified using the nomenclature defined for ‘Object
Specification’ (ObjSpec) in SEMI E39 (Object Services Standard) within the scope of SEMI E40 (Note: see
OBJSPEC in SEMI E5). This use of the ObjSpec nomenclature is required to unambiguously identify parameters
within some complex recipes (e.g., cluster tool process recipes). If the specification of a recipe parameter is
unambiguous, then the form of the ObjSpec may be simplified to just the parameter name. Using the ObjSpec
nomenclature for SEMI E40 recipe parameter names requires an object model to describe equipment recipe
structure.
7.5.5 Figure 1 shows an example of a typical set of cluster tool hierarchical recipe relationships. A processing
parameter might be specified through Sequence Step AB, Process Recipe BB, Process Step CB, to Process
Parameter DB. In this example, the object specifier for Process Parameter DB would be:
“Sequence:Erma>SequenceStep:AB>ProcessRecipe:
BB>ProcessStep:CB>ProcessParameter:DB>”
or
“Erma>AB>BB>CB>DB>”
SEMI E40-0705 © SEMI 1995, 2005 8
Sequence
Erma
SS
AA
Sequence Step
(SS)
AB
SS
AC
PR
BA
Process Recipe
(PR)
BB
PR
BC
PS
CA
Process Step
(PS)
CB
PS
CC
PP
DA
Process Parameter
(PP)
DB
PP
DC
Figure 1
Cluster Tool Sequence Recipe Hierarchical Relationships
7.6 Processing Material Groups — Many equipment architectures require concurrent processing of groups of
material. A single process job can control a group of material, with certain restrictions. All material in the group
needs to be of the same type and processed identically. The processing of each material should be dependent on the
arrival of the group. That is, the full material group shall be received by the equipment before processing begins and
may not depart until all processing is complete. This ensures that the process job remains a simple logical control
mechanism while maintaining robust control, good coordination with material movement, and effective material
data tracking.
7.6.1 Two common examples of allowable material group processing are:
a) an equipment receiving a cassette of wafers to be processed identically. All the wafers in the group are received
together, in the cassette. The processing of the wafers may or may not be simultaneous but can only proceed
once the cassette has arrived. All wafer processing shall complete before the cassette may be removed. Note
that this may alternatively be specified as a simple process job with the cassette as the material; and
b) a cluster tool batch process module processing wafers together. Wafers are received singly. Processing of the
wafer group in the batch chamber begins when all the wafers specified in the process job have arrived. Wafers
are sent after processing is complete.
7.7 Concurrent Process Jobs — Concurrent process jobs is the situation where multiple jobs are active (not queued)
at the same time. A single process job is not always appropriate for concurrent processing of multiple material. In
such cases, multiple concurrent jobs shall be supported by the processing resource. Support of concurrent process
jobs is not a fundamental requirement.
7.7.1 An example of concurrent wafer processing which may not be achieved with a single process job is a carousel
type cluster tool process module. The processing of a single wafer is not dependent on the arrival of the group. In
this case, concurrent process jobs would be created, one for each wafer, even if they were to be processed
identically. This allows effective control and tracking of the process jobs.
7.7.2 Processing management considers concurrent process jobs to be logically independent of one other. They are
distinguished by unique job identifiers. Concurrent jobs may not apply to the same material because the processing
resource may not have more than one active process job associated with a particular material.
7.7.3 There may be interdependencies between concurrent jobs due to resource availability and equipment hardware
architecture.
SEMI E40-0705 © SEMI 1995, 2005 9
7.8 Consecutive Process Jobs — Consecutive process jobs is a situation where multiple process jobs are applied to
material while it is in the processing resource. The process jobs requested on the same material are maintained in the
order received, and a subsequent job becomes active once the previous one has completed material processing.
7.8.1 A process job normally specifies all the processing to be applied to the material during a single visit to the
processing resource. For example, a process job for a cluster tool would specify all the processing in the multiple
sequential steps in the various process modules of the tool. Certain situations may require application of subsequent
process jobs to material without it leaving the processing resource.
7.8.2 Processing management requires that a subsequent process job on the same material does not interrupt the
previous process job processing. The previous process job terminates immediately once it completes active material
processing, even though the material has not left the processing resource, and it is superceded by the subsequent job.
The material becomes associated with the superceding process job. This allows sequential processing and maintains
a single active association between material and process job.
7.9 Process Job without Material — This standard is primarily intended for the management of material processing.
However, it permits application of a process job to a processing resource which contains no processing material.
This may be used to achieve processing resource conditioning which is not related to a specific material.
7.9.1 The process job has the normal control characteristics, except that it has no dependency on material arrival
and terminates at the end of active processing. Support of process jobs without material is not a fundamental
requirement.
8 Behavior
8.1 This section provides a high-level definition of the communications between the supervisor and the processing
resource needed to achieve material processing. It does not define the message detail, concentrating instead on the
concepts. The message detail is addressed in §10, Messaging Services.
8.2 Process Job Communications
8.2.1 Process Job Control Messaging — The control message flow for normal operation is presented in Figure 1.
The arrows represent significant information exchange.
8.2.1.1 A detailed description of each message used in normal operation follows.
8.2.1.2 PR Job Create — The supervisor requests that the processing resource perform the specified process job.
This request may be acted upon immediately, or queued for later execution if the processing resource is busy or the
order of material arrival unknown. If the processing resource does not support queuing or the queue is full, the
request may be rejected. The request shall supply a process specification in which the supervisor supplies such
information as:
identification of the material to be processed,
the recipe defining the processing, and
whether processing will be started manually (optional, normal operation is automatic).
8.2.1.2.1 Upon receipt of the PR Job Create request and before acknowledging, the processing resource checks the
process specifications to ensure that they are valid (i.e., that the specified parameters (recipe, material, manual start)
are sufficient) and have legal values for the capabilities of the processing resource. Depending on its ability to queue
jobs, it may also check such dynamic information as availability of the processing resource to receive the material or
presence of correct material, etc., to determine whether to accept or reject.
8.2.1.2.2 The processing resource sets the process start attribute if automatic start is requested (normal operation).
8.2.1.3 PR Job Create Acknowledge — The processing resource informs the supervisor that the requested job is
accepted or rejected, and if rejected, supplies error codes and textual reasons for the failure.
8.2.1.4
PR Job Setup — The processing resource reports that the process job is active and setting up for process. It
may have been on the queue or have just been created. If the material is not already present, the processing resource
performs any pre-conditioning required then awaits material arrival. Upon arrival of all the material, it prepares for
processing and automatically initiates processing if the process start attribute is set.