semi合集-English.pdf - 第7854页
SEMI T13-1104 © SEMI 2004 14 10.5.3 Die Trace Manager (Manager) — This class represents managem ent entity in Die Trace System and a kind of a br oker among Die Tracers. 10.5.3.1 Responsibility of Die Trace Manager — Thi…
SEMI T13-1104 © SEMI 2004 13
Collaboration is reflected on some association of this
class with others. The collaboration may happen when
some service on this class is requested if the service
needs some related service on any associating class to
complete the original service. They are described in a
part of service definitions above. State model is the
other part of representation of the behavior of this class.
Because this class is stateless, this class defines no state
model.
10.5.2 Die Tracer (Tracer) — This class represents
data collector for die tracing. The data come from Die
Trace Machine or some other entities in the system.
10.5.2.1 Responsibility of Die Tracer — It keeps
collected data somewhere in the system by any means.
However it may have shared database with some other
colleagues to keep the data, this document doesn’t
specify anything about that. How collected data are
managed is out of the scope of this specification and
this document define as much as possible for the case it
has independent data management.
DieTracer
collectDTD
planDTD
showDTD
setForward
catchDTD
enroll
takeDTD
Figure 12
Die Tracer Class
10.5.2.2 Services of Die Tracer — Die Tracer provides
the following services to accomplish its responsibility.
10.5.2.2.1 collectDTD — This optional service collects
further Die Trace Data from data sources, if
subordinates Die Trace Data source has the data, and
replies. If something takes time to collect, it replies
immediate data as much as it has and reports later when
the data is available.
10.5.2.2.2 planDTD — This optional service provides
a capability to set which data are required to be
acquired. If anticipated data cannot be acquired because
such data may not be supplied on specific equipment, it
doesn’t accept this request. It may take time if it needs
to ask process machines whether it has the capability to
provide specified data. Die Tracer replies information
that the service request is acknowledged but detail
possibility is notified later in such cases. This is an
optional service and the means how to specify specific
data item is out of scope of this document because it is
dependent to equipment. If reported data are fixed by
implementation, this service has no effect at all.
10.5.2.2.3 showDTD — This service replies requested
Die Trace Data. Tracer may ask requested data to its
data source before it replies when enough data is not
there. If requested data is not on the tracer and it is
difficult to acquire, it replies no data. If the data item is
strange for the Tracer, it may ask peer Tracer
acquainted or DieTraceManager.
10.5.2.2.4 setForward — This optional service
forwards a part of or all Die Trace Data to specific URI.
Forwarding data should be selectable by category, data
type or originating machine. Also whether the
forwarded data is left on the object or removed should
be selectable. This service is optional and typically used
for specific application or at the time data buffer is
almost full. Interface to receive the data on the URI,
means to send (e.g. SMTP and file transfer) from this
object and application of the data on the URI are out of
the scope of this document. If specified transferring
means is not familiar with this service, an error will be
returned.
10.5.2.2.5 catchDTD — This optional service receives
forwarded Die Trace Data. Die Tracer shall handle the
data without confusion with regular Die Trace Data
coming from subordinate Machines. Usage, purpose
and application of the data are out of the scope of this
document.
10.5.2.2.6 enroll — This optional service registers
specified Die Trace Manager as its supervisory
Manager. Because the manager is only one for the
tracer, this service is used to take over the role of the
Die Trace Manager for the Tracer. This service doesn’t
affect if implementation fixes the Manager.
10.5.2.2.7 takeDTD — This service receives Die Trace
Data from its subordinate Machines. This service is a
notification service and it may be realized by event
subscription of a kind of event channel facility for
particular implementation.
10.5.2.3 Behavior of Die Tracer — Behavior is defined
to complete responsibility of the Die Tracer. The
behavior is often specified through collaboration with
outside of this class and state model. Collaboration is
reflected on some association of this class with others.
The collaboration may happen when some service on
this class is requested if the service needs some related
service on any associating class to complete the original
service. They are described in a part of service
definitions above. State model is the other part of
representation of the behavior of this class. Because this
class is stateless, this class defines no state model.
SEMI T13-1104 © SEMI 2004 14
10.5.3 Die Trace Manager (Manager) — This class
represents management entity in Die Trace System and
a kind of a broker among Die Tracers.
10.5.3.1 Responsibility of Die Trace Manager — This
object manages all Die Tracers in Die Trace
Management Cell which is the range of the manager.
Die Trace Manager repeats asking all Die Tracers when
inquiry about Die Trace Data. Also Die Trace Manager
may participate a network of Die Trace Managers for
more information exchange of Die Trace Data. When
some information or inquiry comes, it may forward it to
the other network members.
DieTraceManager
admit
resign
devolve
logExeption
Figure 13
Die Trace Manager Class
10.5.3.2 Services of Die Trace Manager — Die Trace
Manager provides the following services to complete its
responsibility.
10.5.3.2.1 admit — This service accepts a Die Trace
Manager to be a member of its network for Die Trace
Managers. In the network Die Trace Data are shared
even if they may be stored on different hardware
entities or different network segments. When some
inquiry comes to one of the member of the network, it
broadcasts the inquiry to the other members if it has no
corresponding data locally or there must be further data
in the network. A member of the network who knows
the data replies to the inquirer. If the data is private for
its owner, no reply may be given or notice with
negative reason may be responded. Some member may
be located outside of intranet. Network security and
authentication/authorization are outside of the scope of
this document, and final users of this standard or
network solution providers shall take care this issue to
prevent serious problems.
10.5.3.2.2 resign — This service accepts a member Die
Trace Manager to resign from Die Trace Managers
network. If requested Die Trace Manager has not been a
member, this service replies just error information.
10.5.3.2.3 devolve — This optional service accepts all
or a part of Die Tracers transferred from a Die Trace
Manager as subordinates of this Die Trace Manager.
This manager ask a service of each devolved Tracer to
enroll its subordinate. Before the enrollment has not
been completed the Tracers may report Die Trace Data
to previous Manager. The manager is recommended to
forward the data to the new Manager.
10.5.3.2.4 logExeption — This optional service logs
specified message for errors, peculiar events and other
exceptions happened on each Die Tracer. The logged
information shall be kept for some fair period and/or
displayed on the console of the computer or its remote
terminal window. This service is typically used for
resource-less Die Tracers or concentrated exception
monitoring.
10.5.3.3 Behavior of Die Trace Manager — Behavior
is defined to complete responsibility of the Die Trace
Manager. The behavior is often specified through
collaboration with its outside and state model.
Collaboration is reflected on some association of this
class with others. The collaboration may happen when
some service on this class is requested if the service
needs some related service on any associating class to
complete the original service. They are described in a
part of service definitions above. State model is the
other part of representation of the behavior of this class.
Because this class is stateless, this class defines no state
model.
10.5.4 Die Trace Machine (Machine) — This class
represents production equipment to be source provider
of Die Trace Data including process, metrology, test,
material handling, assembly, packaging, mounting and
any means used for manufacturing. Even handwork
process could be the Machine as long as it records work
and data during the work electrically, if such data are
effective for Die Tracing purpose.
10.5.4.1 Responsibility of Die Trace Machine — This
object reports expected Die Trace Data to Die Tracer.
10.5.4.2 Services of Die Trace Machine — Die Trace
Machine provides the following services to complete its
responsibility.
DieTraceMachine
acquireDTD
setPlanningItems
flush
registerTracer
Figure 14
Die Trace Machine Class
10.5.4.2.1 acquireDTD — This service provides
expected Die Trace Data on production equipment. It
reports corresponding data immediately if the data has
SEMI T13-1104 © SEMI 2004 15
been already available on the equipment. If not, it
acquires the data before reporting. If the acquisition
was impossible, no data is replied.
10.5.4.2.2 setPlanningItems — This service specifies
expecting data items for die tracing. The items are
chosen from potential and reportable data list for die
tracing in specification exchanged between equipment
vendor and user. Otherwise both party need to prepare a
kind of metadata which describes reportable data items
and their properties including data sources equipment
itself electrically to allow user’s application to specify
expecting data item by looking up the metadata.
10.5.4.2.3 flush — This optional service let equipment
send all planned data which have been already acquired
but not sent yet. Same data will responded with
acquireDTD service if all planned data items are
specified. This service is typically used when the Tracer
of this Machine is replaced.
10.5.4.2.4 registerTracer — This optional service
allows switching corresponding Tracer dynamically.
10.5.4.3 Behavior of Die Trace Machine — Behavior
is defined to complete responsibility of the Die Trace
Machine. The behavior is often specified through
collaboration with its outside and state model.
Collaboration is reflected on some association of this
class with others. The collaboration may happen when
some service on this class is requested if the service
needs some related service on any associating class to
complete the original service. They are described in a
part of service definitions above. State model is the
other part of representation of the behavior of this class.
Because this class is stateless, this class defines no state
model.
11 Suggestive Complements
11.1 Illustrative Models in Production Line — Device
Tracking needs to cover throughout production line
widely from very early stage of materials through
almost final product for consumers. However specific
production systems may be somewhat different
depending on stages, the following models illustrate
typical issues in interrelation between production and
tracking.
11.2 Data around Machine and Circuit Module —
There are many acquired or measured data and context
information of such production systems as
Manufacturing Execution System (MES) and Work In
Process (WIP). Each data or information could be
independent or a part of Die Trace Data.
11.2.1 Obtained Data — Many sorts of data can be
obtained on each piece of equipment. A part of the data
or the summarized/processed data could be Die Trace
Data.
11.2.1.1 Examined Data — If Die Trace Machine is
metrology, inspection or test equipment, measured,
inspected or tested result data is obtained on the
equipment respectively. Such data as a whole, a part of
the data or even the data which is
summarized/processed, it could be a kind of Die Trace
Data. As long as the equipment has one or more
modules which have such functions, the equipment can
provide the data even if it has process capability.
Circui t Module
Die
Mother
Substrate
0..*
Die Trace Data
(DTD)
characterizes
0
..*
refers
links
0
..*
Production Job
Die Trace
Machine
Recipe
Adjusted
Par ame te r
Examined Data
Acquired Data
provides
compensates
measures
on
pr ocess es
on
s
p
ecifies
specifies
specifies
specifies
0
..*
0
..*
0
..*
processe
d
or
measured
0..1
0
..1
0
..1
Figure 15
Possible Die Trace Data around Machine and Circuit Module