semi合集-English.pdf - 第2809页

SEMI E102-0600 © SEMI 2000 17 Exceptions: exception UnsupportedDestinationTypeSignal {} ; Published Events: None. Provided Services: The Creation of TransportJobs is accom plished b y use of the requ es tJob operation f …

100%1 / 7923
SEMI E102-0600 © SEMI 2000 16
/* An attempt was made to locate an unknown Machine. */
exception MachineNotFoundSignal {string machineName;};
exception MachineRemovalFailedSignal {};
Published Events:
/* Event indicating that a Machine has been added or removed from the Factory. */
MachineListChangedEvent
Provided Services:
/* Add a Machine to the set of machine(s) managed by the MachineRegister. */
void addMachine (in Machine aMachine)
raises (Global::FrameworkErrorSignal);
/* Remove a Machine from the set of machine(s) managed by the MachineRegister. */
void removeMachine (in Machine aMachine)
raises (Global::FrameworkErrorSignal,
MachineRemovalFailedSignal);
/* Return a sequence of all machines managed by the MachineRegister. */
MachineSequence allMachines ()
raises (Global::FrameworkErrorSignal);
/* Return the Machine corresponding to the given name. */
Machine findMachineNamed (in string identifier)
raises (Global::FrameworkErrorSignal,
MachineNotFoundSignal) ;
Contracted Services: None.
Dynamic Model: None.
}; // MachineRegister
6.3 Material Transport Abstract Interfaces — The Material Transport Abstract Interfaces are defined to perform
material transport at the factory level. The TransportJobSupervisor interface must be specialized by the users of the
Material Transport Manager Interface. These interfaces provide a way to track the job through the factory.
6.3.1 TransportJobSupervisor Interface
Module: MaterialTransport
Interface: TransportJobSupervisor
Inherited Interface: JobSupervisor
interface TransportJobSupervisor : AbstractIF::JobSupervisor {
Description: TransportJobSupervisor is an abstract interface which provides the operations needed by
clients to request, track, and control material transport within the domain of the specific
TransportJobSupervisor. Any entity which is responsible for moving material will inherit
and implement TransportJobSupervisor.
Type Definitions:
typedef sequence <Global::Properties> JobSpecSequence;
SEMI E102-0600 © SEMI 200017
Exceptions:
exception UnsupportedDestinationTypeSignal {};
Published Events: None.
Provided Services:
The Creation of TransportJobs is accomplished by use of the requestJob operation from the inherited JobSupervisor
interface. The “JobType” property specified in the inherited interface should be set to “TransportJobType” for all
TransportJob requests. The additional Job Specification properties required for the creation of Transport jobs are
defined in Table 3. The types of machines specified in the TransportJob are AMHS Storage Machines, Fixed Buffer
Production Equipment, or Internal Buffer Production Equipment. Each machine type represents a separate case used
in defining the Job Specification for a Transport Job, and these cases are also defined in Table 3.
For transportJobs, the inherited ABORTING and ABORTED states may not always result in an immediate
termination of the job and associated activities. For example, transportJobs may involve autonomous transport
equipment that operate without persistent communication links to the TransportJob and TransportJobSupervisor
objects. In these cases there may be a time delay before the results of a transportJob makeAborted request can be
enacted to allow the transport equipment to reach a known location. In other cases a movement activity must reach a
stable condition before it can be interrupted. The location of the MaterialContainer associated with the aborted
TransportJob is the nearest location where movement can be safely and reliably interrupted.
By contrast, if a transportJob is transitioned to the inherited STOPPING state, the location of the MaterialContainer
associated with the stopped TransportJob must be a legal Source for issuing a new TransportJob.
Table 3 Additional Required Properties for Transport Jobs
Name Value Type Description
“Container” MaterialContainer Container being transported.
“SourceMachine” Machine The source production machine for the transport job.
AMHS Storage Equipment: SourceMachine is Optional.
Fixed Buffer Production Equipment: SourceMachine is Required.
Internal Buffer Production Equipment: SourceMachine is Required.
“SourcePort” Port The source production machine port for the transport job.
AMHS Storage Equipment: SourcePort is Optional.
Fixed Buffer Production Equipment: SourcePort is Required.
Internal Buffer Production Equipment: SourcePort is optional. Port may be
obtained dynamically with the containerOut operation or it may be predefined
in the TransportJob specification.
“DestinationArea” Area The destination area for the transport job. DestinationArea shall contain only
StorageMachines. The implementation shall determine the specific machine to
which the MaterialContainer is delivered.
AMHS Storage Equipment: DestinationArea is optional.
Fixed Buffer Production Equipment: DestinationArea is not allowed.
Internal Buffer Production Equipment: DestinationArea is not allowed.
“DestinationMachine” Machine The destination machine for the transport job.
AMHS Storage Equipment: DestinationMachine is required if DestinationArea
is not specified.
Fixed Buffer Production Equipment: DestinationMachine is required.
Internal Buffer Production Equipment: DestinationMachine is required.
SEMI E102-0600 © SEMI 2000 18
Name Value Type Description
“DestinationPort” Port The destination port for the transport job.
AMHS Storage Equipment: DestinationPort is required for Manual output port
destinations.
Fixed Buffer Production Equipment: DestinationPort is required.
Internal Buffer Production Equipment: DestinationPort is NULL.
/* The requestBatchTransportJob operation will provide two or more job specifications for transport jobs that share
a dependency on completion. All job specifications must have the same priority. In the normal case, the
TransportJobSupervisor will create simple transport jobs for each job specification and return the jobs as a sequence.
Subsequently, if one of the simple jobs cannot complete, the other subordinate jobs must be reassessed by the
JobRequestor to determine the appropriate corrective action. In this case, the TransportJobSupervisor will notify the
JobRequestor of the job failure with the informJobTerminated message and pause the other jobs of the batch-job to
allow the JobRequestor to determine its response. Implementations may implement the TransportJobSupervisor with
more complex default actions in response to a partial failure of a batch-transport-job, but these more complex
scenarios are not part of the standard behavior for this operation. */
AbstractIF::JobSequence requestBatchTransportJob (
in JobSpecSequence jobSpecs,
in AbstractIF::JobRequestor aJobRequestor)
raises (Global::FrameworkErrorSignal,
AbstractIF::JobSupervisor::JobRejectedSignal);
Contracted Services: None
Dynamic Model: None
}; // TransportJobSupervisor
6.4 Material Transport and Storage Component
6.4.1 This component is concerned only with factory-wide material transport and not the movement of material
within a piece of equipment. Also note that material can be either product, durables, or consumables. The CIM
Framework recognizes the potential for multiple AMHS’s within a single factory (e.g., one supplier of interbay
movement and another supplier of intrabay movement). The MES, however, wants to only have to issue a move
request (“move this material from here to there”) without regard to whether that transport spans one or more
AMHS’s. Therefore, the component supporting material transport requires a single entry point for initiating material
transport which will be through the Material Transport Manager (MTM).
6.4.2 The Material Transport Manager must be able manage transport jobs carried out by many different AMHS’s.
To accomplish this, a separate interface for a Material Transport Controller (MTC) is specified. In the simplest
implementations, a single MTM may manage all TransportJobs directly. In this case no separate Material Transport
Controller implementation is needed. If there is a need for delegation to one or more Material Transport Controllers,
the Material Transport Manager can register any conformant MTC implementation which supports the specified
interface. The low-level interaction of the material movement controllers with the physical equipment (transport
machines, storage machines and ports) is encapsulated within the scope of this component. Note that the component
manager does not provide lifecycle services for its managed material movement controllers, but instead uses the
registration interfaces.
6.4.3 MaterialTransportManager Interface
Module: MaterialTransport
Interface: MaterialTransportManager
Inherited Interface: ComponentManager, TransportJobSupervisor, JobRequestor
interface MaterialTransportManager : FactoryOperations::ComponentManager,
TransportJobSupervisor, AbstractIF::JobRequestor {