semi合集-English.pdf - 第2743页
SEMI E98-1102 © SEMI 2000, 2002 8 7.3 Computer Manufacturin g Integratio n Business Goals 7.3.1 The intent of this section is to provide a co ntext for, and insight into, those requirements of industries such as semicond…
SEMI E98-1102 © SEMI 2000, 2002 7
6.4.3 Service Message Definition
6.4.3.1 A service message definition table defines the parameters used in a service, as shown in the following table:
Parameter Req/Ind Res/Cnf Comment
6.4.3.2 The columns labeled REQ/IND and RSP/CNF 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” or the request.
The receiver may then send a “Response” which the original sender terms the “Confirmation”.
6.4.3.3 The following codes appear in the REQ/IND and RSP/CNF columns and are used in the definition of the
parameters (eg., how each parameter is used in each direction):
M Mandatory Parameter — Must be given a valid value.
C 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 value of the other parameter.
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 OBEM Standard Structure
6.5.1 The remaining part of this document is organized as follows:
6.5.1.1 Section 7 contains background information to provide a context for the Object-Based Equipment Model.
6.5.1.2 Sections 8 provides an overview of two major views of the equipment: the functional view and the internal
composition view.
6.5.1.3 Section 9 introduces the OBEM object model: the interface inheritance hierarchy and the rules of
aggregation that together form the foundation of the OBEM model of equipment.
6.5.1.4 Section 11 defines the requirements for the component objects within the equipment interface hierarchy: and
other related objects of significance not defined elsewhere.
6.5.1.5 Section 12 defines the message services used in OBEM that are not defined in other standards.
6.5.1.6 Section 13 defines the services that are required of the user (factory system, remote access, and operator).
6.5.1.7 Section 14 specifies the minimum requirements and optional capabilities for compliance to the OBEM
standard.
6.5.1.8 Section 15 provides scenarios showing typical message flows during operation.
6.5.2 Additional sections are provided as related information: examples and additional material that are not part of
the standard itself. These include models for linked litho, 300 mm equipment, the relationship of OBEM and the
CIM Framework, and representations of date and time.
7 Background
7.1 Both modern manufacturing processes and modern manufacturing equipment are increasingly complex. A
single installation of equipment may have hundreds or thousands of sensors and actuators. In order to manage this
complexity, better methods of referencing the internal components of equipment are needed. Use of the object
paradigm provides a means for the equipment to describe its internal composition to the factory in a natural way.
7.2 Definition of standardized objects allows the factory to be specific about its requirements and its need for
information.
SEMI E98-1102 © SEMI 2000, 2002 8
7.3 Computer Manufacturing Integration Business
Goals
7.3.1 The intent of this section is to provide a context
for, and insight into, those requirements of industries
such as semiconductor and flat panel display (FPD)
manufacturing businesses that affect the object-based
equipment model.
7.3.2 The primary purpose of computer integrated
manufacturing (CIM) technologies is to improve
factory productivity.
4
Other inter-related secondary
CIM business goals are listed below.
• Maximize product yields (line/mechanical yield).
• Maximize device yields (electrical/functional
yield).
• Maximize total factory product substrate
throughput.
• Increase individual equipment product substrate
throughput.
• Reduce product variability.
• Reduce process variability.
• Optimize ability to center processes in a “sweet
spot”.
• Reduce the use of non-product substrates.
• Reduced time to utilization for equipment (i.e., the
time to install, qualify, characterize and ramp
production).
• Increase the usability, accuracy, and reliability of
data used for metrics.
• These business goals can be met by addressing
certain concrete objectives, which are listed below.
7.4 OBEM Functional Objectives
7.4.1 OBEM will standardize specific functional
capabilities to be implemented on semiconductor/FPD
and other manufacturing equipment, providing a
hierarchical view of equipment for effective factory
integration.
7.4.2 The OBEM functional objectives are as follows:
• Manage material into and through the equipment.
• Manage the association of the process instructions
with the material.
4 For a more detailed discussion and list, see the Guidance and
Guideline documents at
http://www.sematech.org/public/docubase/abstract/tech-30.htm
• Report data associated with the equipment, the
process, and the material.
• Facilitate equipment performance monitoring.
7.4.3 These OBEM functional objectives, individually
and collectively, can be shown to directly address the
overall business goals:
7.4.4 The Object Based Model objective directly
affects the ability to implement most of the other
objectives, especially in the case of highly modular
equipment.
7.4.5 Equipment performance monitoring has the effect
of improving product variability, device yield and can
reduce the need for non-product test substrates. It can
also provide a means of targeting a specific process
window to improve device characteristics such as
speed.
7.4.6 Management of the association of process
instructions with the material can reduce scrap due to
misprocessing, thus improving product yield. The
material management objectives impact on the
throughput of individual equipment and the total
factory throughput.
7.5 Relevant Factory Environment — Equipment must
support a variety of different factory environments.
This is necessary because factory business practices and
factory configurations vary not only from company to
company but also from one facility within a company to
another. Items will be added to this section as their
relevance becomes apparent.
7.5.1 Material Handling Systems — Material may be
loaded and unloaded manually by a fab technician or it
may be loaded and unloaded using semi-automated and
automated transport systems. Types of systems
include:
• Automated Guided Vehicles (AGV),
• Personal Guided Vehicles (PGV),
• Overhead Transport Systems (OTS), including
Overhead Hoist Transport (OHT), and
• Fixed Arm Robots.
7.5.2 Containers — Containers may be open (e.g.,
cassettes) or closed (pods, including reticle pods). Pods
may be bottom-opening (SMIF), with a removable
cassette, or front-opening (FIMS), which may have
either a removable cassette or an integrated (non-
removable) cassette (FOUP).
7.5.3 Factory Interface — The equipment must be able
to support different levels of automation, including:
SEMI E98-1102 © SEMI 2000, 2002 9
• stand-alone (with no connection to the factory
systems),
• fully on-line and operated locally (by the operator),
• fully on-line and operated remotely (by the factory
systems), and
• fully on-line and able to support and coordinate
interactions from multiple factory users and
systems at the same time.
8 Equipment Overview
8.1 The Object-Based Equipment Model defines the
objects that are generic components of equipment as
well as the object representing the equipment itself.
OBEM does not dictate the makeup of equipment.
Through support of OBEM, the equipment is able to
describe its own makeup to the factory. However,
OBEM does require certain visibility and access to
those parts of the equipment that control and/or monitor
the environment or the location of the product.
8.2 Two view areas are of importance: the functional
view of the equipment and the internal composition
view of the equipment.
8.3 Functional View of Equipment — From a
functional view, equipment is internally composed of
logical subsystems with different areas of responsibility
that are at different levels within a control hierarchy, as
illustrated in Figure 1. There are three general levels.
Equipment Control is at the highest level, both respon-
sible for, and representing, the equipment as an inte-
grated whole. The middle level provides management
of specific areas, while the lowest level of functionality
has specific time-critical responsibilities and handles all
direct interaction with the equipment’s I/O (sensors and
actuators). The third level is below the factory level of
visibility and is discussed here for completeness.
NOTE 3: This is not intended to represent the design of an
actual implementation.
8.3.1 The functional areas are discussed below in
alphabetical order.
8.3.2 Access Management — Access Management is
responsible for communications with the factory,
including factory computers, local and remote oper-
ators, third party systems, and alternate users (desktop
access by process engineers, maintenance personnel,
supplier remote diagnostics, etc.) Communications
with the local operator include input devices (such as
keyboards, wands, buttons, and optical character read-
ers) and display devices (console, light pole, and LCD
panel) as well as interpretation of operator requests.
8.3.3 Communications Link — Communications Link
is responsible for low-level communications, including
establishing a connection with a communications
partner, sending messages, and receiving messages.
8.3.4 Date/Time Management — Date/Time Manage-
ment is responsible for maintaining an accurate date
and time-of-day, and for providing current date/time
information to the rest of the system. This may include
maintenance of regular time-based scheduling.
8.3.5 Environment Control — Environment Control is
responsible for maintaining the internal environment
according to the equipment’s specifications. While
Process Control is specific to a process and recipe,
other monitoring activities may be required regardless
of whether the equipment is processing or idle. Such
activities include monitoring for particles, humidity, or
temperature.
8.3.6 Equipment Control — Equipment Control is the
supervisory level with overall high-level control.
Equipment Control represents the entire equipment as
an integrated whole to the factory and represents the
decision-making authority within the equipment.
8.3.7 Event Management — Events continually occur
in all equipment states. A variety of these events are of
interest to the factory, including those events that
generate a change of state in any standardized object.
The factory requires notification when selected events
occur, and in many cases, requires reports of the values
of specified information at the time that the event
occurred. Event Management is responsible for
tracking those events and the reports associated with
those events.
8.3.8 Exception Management — Exception Manage-
ment is responsible for determining the proper response
to an action or operation that the equipment was unable
to perform which raised an exception condition. It
prompts notification to all affected components,
including internal components and currently connected
users. In some cases, the proper action may have to be
resolved by the user. Exception Management is a high
level activity that is in addition to underlying hardware
and software interlocks.