semi合集-English.pdf - 第2811页

SEMI E102-0600 © SEMI 2000 19 Description: A MaterialTransportManager (MTM) operates on requests to move material in the factory. It returns a T ransportJob to the requestor, allow i ng the requestor to track the status …

100%1 / 7923
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 {
SEMI E102-0600 © SEMI 200019
Description: A MaterialTransportManager (MTM) operates on requests to move material in the
factory. It returns a TransportJob to the requestor, allowing the requestor to track the
status and progress of the move. The MTM may perform these TransportJobs by breaking
them into separate tasks to be performed by MaterialTransportControllers (MTC). If
TransportJobs are decomposed, the MaterialTransportManager then tracks the MTC
TransportJobs to fulfill its commitment.
Exceptions:
exception MaterialTransportControllerNotRegisteredSignal {};
Published Events: None.
Provided Services:
/* Add a MaterialTransportController to the collection of MaterialTransportControllers which the
MaterialTransportManager can use to carry out jobs. */
void registerMaterialTransportController (
in MaterialTransportController aMaterialTransportController)
raises (Global::FrameworkErrorSignal);
/* Remove a MaterialTransportController from the list of resources available to the MaterialTransportManager. No
new jobs will be issued but existing jobs will be unaffected. */
void unregisterMaterialTransportController (
in MaterialTransportController aMaterialTransportController)
raises (Global::FrameworkErrorSignal,
MaterialTransportControllerNotRegisteredSignal);
/* Return a list of all MaterialTransportControllers managed by the MaterialTransportManager. */
MaterialTransportControllerSequence allMaterialTransportControllers ()
raises (Global::FrameworkErrorSignal);
/* Returns a list of all material in the material transport system. */
AbstractIF::MaterialSequence allMaterial ()
raises (Global::FrameworkErrorSignal);
/* Returns a list of all material in transit in the material transport system. */
AbstractIF::MaterialSequence allMaterialInTransit ()
raises (Global::FrameworkErrorSignal);
/* Returns a list of all material in storage in the material transport system. */
AbstractIF::MaterialSequence allMaterialInStorage ()
raises (Global::FrameworkErrorSignal);
Contracted Services: None
Dynamic Model: None
}; // MaterialTransportManager
6.4.4 MaterialTransportController Interface
Module: MaterialTransport
Interface: MaterialTransportController
Inherited Interface: TransportJobSupervisor
interface MaterialTransportController : TransportJobSupervisor {
SEMI E102-0600 © SEMI 2000 20
Description: A MaterialTransportController accepts transport job requests, schedules them, and
executes them in order to move material around the factory or a part of the factory.
Exceptions: None.
Published Events: None.
Provided Services:
typedef sequence <MaterialTransportController> MaterialTransportControllerSequence;
/* Returns a list of all material in the domain of this material transport controller. */
AbstractIF::MaterialSequence allMaterial ()
raises (Global::FrameworkErrorSignal);
/* Returns a list of all material in transit in the domain of this material transport controller. */
AbstractIF::MaterialSequence allMaterialInTransit ()
raises (Global::FrameworkErrorSignal);
/* Returns a list of all material in storage in the domain of this material transport controller. */
AbstractIF::MaterialSequence allMaterialInStorage ()
raises (Global::FrameworkErrorSignal);
Contracted Services: None
Dynamic Model: None
}; // MaterialTransportController
6.4.5 TransportJob Interface
Module: MaterialTransport
Interface: TransportJob
Inherited Interface: Job
interface TransportJob : AbstractIF::Job {
Description: This type of Job performs a specific transport of material. The ongoing status of the move
can be monitored by subscribing to the appropriate Job events.
Exceptions:
exception TimeUndeterminableSignal {};
Published Events: Same as Job
Provided Services:
/* Determine if the move can be completed by the specified time. */
boolean canCompleteBy (
in Global::TimeStamp whenNeeded)
raises (Global::FrameworkErrorSignal,
TimeUndeterminableSignal);
/* Estimate how long this job will take once it begins. */
Global::Duration transportTime ()
raises (Global::FrameworkErrorSignal,
TimeUndeterminableSignal);