semi合集-English.pdf - 第1630页

SEMI E38-1296 © SEMI 1995 , 1996 19 The specific obj ect types , relations, attributes, and access rules are def ined in each s p ecific services grou p. The object services are def ined in SEMI E39 (Obj ect Services Sta…

100%1 / 7923
SEMI E38-1296 © SEMI 1995, 1996 18
# Current State Trigger New State Action(s)
11 Transferring
Between Modules
Arrived output CM. Arrived output CM CM Input/Output Transfer Job.
12 Arrived output CM Transfer back to factory complete. Processing in cluster
complete
The material is finally unloaded from the output
cassette module to the factory (intertool material
transfer). If all process steps in the cluster tool were
completed and were successful, the processing in the
cluster tool is complete; otherwise, processing in the
cluster tool was only partially accomplished.
Detailed behavioral models are documented in the
individual Cluster-Specific Services and in the
standards which they reference. The Typical Operating
Scenario in the application notes illustrates the
behavioral characteristics of cluster tool control by
showing the detailed messaging among modules and
supervisory controller through the lifecycle of material
as it enters the cluster, is processed, and then leaves the
cluster.
7.4 Cluster Tool Control Topology — The natural
decomposition of a cluster tool is into its modules. The
module controller is the entity which performs internal
control of a module and provides standard services.
Module controllers provide certain application-specific
functions (providers of services and user of services)
and consist of hardware and software components that
interact with the communications and control
environment of the cluster tool.
Traditional definitions of controllers have implied
certain PHYSICAL, hardware control topologies (such
as distributed or centralized processors). These cluster
tool standards specify the communications in terms of
services-providers, enabling the module controllers to
be based on LOGICAL control topologies.
The list of possible physical controllers which could be
used to implement the logical services of the standards
are listed below. It is emphasized, however, that the
standard is not based on any constraint that each of
these physical controllers be present in a cluster control
system, but instead requires that the logical services
(i.e., software functional components) be present
somewhere in the cluster control system.
Possible Controllers:
• Cassette Module Controller
• Process Module Controller
• Transport Module Controller
• Cluster Controller
The logical control topology allows any combination of
module controllers on a single control unit. Standard
communication is not required among them. A common
example is the grouping of transport module and
cassette module control into a single material handler
control unit as shown in Figure 1. For interface
compliance, all communication between a logical
module controller and remote controller or service-user
must be compliant with the standard services.
8 Cluster Tool Module Serv ices
The Cluster Tool control system elements, as
represented in the object information, object
communications, and behavioral models, require
standard services in order to interface with one another.
The objects which are fully standardized (attributes,
behavior, and operations) are only those essential to this
communication, and the services are the interactions
with these standard objects.
The services are grouped into the following functional
areas:
• Object Services
• Processing Management
• Material Movement Management
• Exception Management
• Recipe Management
• Event Reporting
• Clock
The services of each of these groups are described in
detail in this section. The services are defined in terms
of services provided by independent SEMI standards,
specifying their application and limitations with respect
to the fundamental requirements of cluster tool module
communications.
8.1 Object Services — All standardized service object
attribute access across a cluster tool module
communications interface is achieved using object
services. Access may be to read attribute values of
objects, to get a list of objects corresponding to certain
criteria, and to set the values of writable attributes of
objects. The message services provided to accomplish
this are Get and Set.
SEMI E38-1296 © SEMI 1995, 199619
The specific object types, relations, attributes, and
access rules are defined in each specific services group.
The object services are defined in SEMI E39 (Object
Services Standard: Concepts, Behavior, and Services).
Cluster tool module communications require only the
fundamental requirements of that standard except where
stated in a specific services group below.
8.2 Processing Management Services — Processing
management across a cluster tool module communica-
tions interface is achieved using the processing
management services. These services provide the
communications and behavior required of the process-
ing resource by the material processing models through
defining the process job object and its operations.
The processing management services follow SEMI E40
(Standard for Processing Management). Cluster tool
module communications require full compliance with
the information, behavior, and messaging services of
the fundamental requirements of that document.
The process job creation is requested by the cluster
controller using the PRJobCreate service. If the
processing resource accepts the job, it performs the
required processing to completion once the material
arrives. The processing resource shall support the
PRJobCommand Abort service, which ceases any
processing and terminates the job. The processing
resource reports process job milestones achieved to the
cluster controller using the PRJobAlert service.
Process job object attributes required to be accessible
through object services follow:
Attribute Name Description: Requirements
ObjType The object type: process job.
PRJobID Identifier for the process job.
PRMtlType MaterialType.
PRMtlNameList Material identifier: single material only.
PRRecipeMethod Recipe specification type: recipeID
only.
RecID Identifier of the recipe applied.
PRJobStateList All concurrent substates of the process
job.
Processing management messaging services required:
Message Name Description: Requirements
PRJobCreate Create process job: single material,
recipe identifier only, auto-start.
PRJobCommand Command on a process job: abort.
PRJobAlert Notification: setup, processing,
processing complete, complete.
Processing resource capabilities required, but not
already specified above:
• Detect and report success or failure of a process
job.
• Reject incomplete, invalid, and unsupported
requests.
Processing resource capabilities permitted, but not to be
required, by a service-user:
• Pre-conditioning and post-conditioning.
• Stop, Pause, and Resume of a process job.
• Manual process start.
• Process job queuing and queued job Cancel.
• Process tuning.
• Processing of material groups.
• Multiple concurrent process jobs.
• Multiple consecutive process jobs.
• Process job with no material.
• Notification of waiting for material and of process
job state changes.
8.3 Material Movement Services — Each material
movement in a cluster tool involves interaction among
the cluster controller and all of the modules
participating in the transfer. The communications
interfaces and behavior resulting from the material
movement models are defined for each association by
the material movement services.
The material movement services are partitioned into
intratool material movement services, intertool material
movement services, and carrier mapping, as in the
models.
The material movement services follow the Material
Movement Management Standard [SEMI E32] and
Object Services Standard: Concepts, Behavior, and
Services [SEMI E39]. Cluster tool module
communications require full compliance with the
information, behavior, and messaging services of the
fundamental requirements of those standards.
8.3.1 Intratool Material Movement Services — From
the intratool material movement models, an intratool
material transfer — the transfer of material from one
attached module to another through a transport module
— requires the following interactions:
1. The cluster controller decides that material is to be
moved as the result of either arrival of material or
the completion of some processing step on the
material. It determines which material is to be
SEMI E38-1296 © SEMI 1995, 1996 20
moved and the source and destination of that
movement (cluster-application-specific). It requests
all the modules involved to perform the appropriate
TM or AM transfer job.
2. The source- and destination-attached modules
inform the transport module that they are prepared
to do their specific activities during the material
transfer. The transport module informs the source-
and destination-attached modules, each at the
appropriate point in time, that it is synchronized for
material handoff.
3. The detailed transactions required to handoff the
material during the transfer are accomplished, first
at the source and then at the destination.
These interactions may require a number of
communications interfaces for intratool material
transfer from the following:
• Cluster controller to transport module
• transfer resource: TM transfer job source AM
to destination AM
• Cluster controller to source-attached module
• intratool port resource: AM transfer job send
• Cluster controller to destination-attached module
• intratool port resource: AM transfer job receive
• Transport module to source-attached module
• intratool port to transfer resource: handoff get
• Transport module to destination-attached module
• intratool port to transfer resource: handoff put
The material movement services define the
communications and behavior required of the attached
module intratool port resource and the transport module
transfer resource. They define the TM transfer job, TM
atomic transfer, AM transfer job, and AM atomic
transfer objects and their operations, as well as the
handoff operations between the transfer resource and
the intratool port resource.
Each interface is described below.
Cluster Controller to Transport Module Interface —
The TM transfer job creation is requested by the cluster
controller using the TRJobCreate service. If the transfer
resource accepts the job, it performs the transfer of the
material to completion, coordinating with the attached
modules. The TM transfer job comprises two atomic
transfers for the material, one to get (receive) it from
the source-attached module and another to put (send) it
to the destination-attached module.
The transfer resource shall support the TRJobCommand
Abort service, which ceases any transfer activity and
terminates the job. The transfer resource reports transfer
job milestones achieved to the cluster controller using
the TRJobAlert service.
The transfer resource coordinates material handoff with
each attached module through the transport
module/attached module interface, described below.
TM transfer job object attributes required to be
accessible through object services:
Attribute Name Description: Requirements
ObjType The object type: transfer job.
TRJobID Identifier for the transfer job.
(Ordered list of)
TRAtomicID
Ordered list of identifiers for the
atomic transfers in the transfer job:
two atomic transfers for the material.
(List of)TRJobState All concurrent substates of the
transfer job.
TM atomic transfer object attributes required to be
accessible through object services:
Attribute Name Description: Requirements
ObjType The object type: atomic transfer.
TRAtomicID Identifier for the atomic transfer.
TRLink Identifier to coordinate handoff.
TRObjType Material Type.
TRObjName Material identifier.
TRRole Role in transfer control: secondary.
TRPartner Identifies partner-attached module.
TRDirection Handoff direction: receive from
source AM, send to destination AM.
TRType Active/passive in transfer: active.
(List of)TRAtomic-
State
All concurrent substates of the atomic
transfer.
Material movement messaging services required:
Message Name Description: Requirements
TRJobCreate Create transfer job: single material,
source to destination AM, auto-start.
TRJobCommand Command on transfer job: abort.
TRJobAlert Notification: started, complete.
Transfer resource capabilities required, but not already
specified above:
• Detect and report success or failure of a transfer
job.