semi合集-English.pdf - 第2859页

SEMI E105-0701 © SEMI 2000, 2001 10 #endif // _CIMFW_SCHEDULING_ }; // mdoule CIMFW NOTICE: SEMI makes no w arra nties or representations as to the suitab ility of the standard set forth herein for any particular applica…

100%1 / 7923
SEMI E105-0701 © SEMI 2000, 20019
ActivityList whatNextForResourceByCount (
in AbstractIF::Resource aResource)
in short listCount)
raises (Global::FrameworkErrorSignal,
ResourceNotFound);
ActivityList whatNextForMaterialGroupByCount (
in AbstractIF::MaterialGroup aMaterialGroup,
in short listCount)
raises (Global::FrameworkErrorSignal,
MaterialGroupNotFound);
ActivityList whatNextForDurableByCount (
in DurablesManagement::Durable aDurable)
in short listCount)
raises (Global::FrameworkErrorSignal,
DurableNotFound);
ActivityList whereNextForMaterialGroup (in AbstractIF::MaterialGroup aMaterialGroup)
raises (Global::FrameworkErrorSignal,
MaterialGroupNotFound);
ActivityList whereNextForDurable (in DurablesManagement::Durable aDurable)
raises (Global::FrameworkErrorSignal,
DurableNotFound);
ForecastList forecastForResourceByTime (
in AbstractIF::Resource aResource,
in Global::TimeStamp lookAheadTime)
raises (Global::FrameworkErrorSignal,
ResourceNotFound);
ForecastList forecastForMaterialGroupByTime (
in AbstractIF::MaterialGroup aMaterialGroup,
in Global::TimeStamp lookAheadTime)
raises (Global::FrameworkErrorSignal,
MaterialGroupNotFound);
ForecastList forecastForDurableByTime (
in DurablesManagement::Durable aDurable,
in Global::TimeStamp lookAheadTime)
raises (Global::FrameworkErrorSignal,
DurableNotFound);
ForecastList forecastForResourceByCount (
in AbstractIF::Resource aResource,
in short lookAheadCount)
raises (Global::FrameworkErrorSignal,
ResourceNotFound);
ForecastList forecastForMaterialGroupByCount (
in AbstractIF::MaterialGroup aMaterialGroup,
in short lookAheadCount)
raises (Global::FrameworkErrorSignal,
MaterialGroupNotFound);
ForecastList forecastForDurableByCount (
in DurablesManagement::Durable aDurable,
in short lookAheadCount)
raises (Global::FrameworkErrorSignal,
DurableNotFound);
}; // SchedulingManager
}; // module Scheduling
SEMI E105-0701 © SEMI 2000, 2001 10
#endif // _CIMFW_SCHEDULING_
}; // mdoule CIMFW
NOTICE: SEMI makes no warranties or representations as to the suitability of the standard set forth herein for any
particular application. The determination of the suitability of the standard is solely the responsibility of the user.
Users are cautioned to refer to manufacturer’s instructions, product labels, product data sheets, and other relevant
literature respecting any materials mentioned herein. These standards are subject to change without notice.
The user’s attention is called to the possibility that compliance with this standard may require use of copyrighted
material or of an invention covered by patent rights. By publication of this standard, SEMI takes no position
respecting the validity of any patent rights or copyrights asserted in connection with any item mentioned in this
standard. Users of this standard are expressly advised that determination of any such patent rights or copyrights, and
the risk of infringement of such rights, are entirely their own responsibility.
SEMI E105-0701 © SEMI 2000, 200111
RELATED INFORMATION 1
IMPLEMENTATION GUIDANCE FOR INPUT OF FACTORY STATE
INFORMATION TO THE SCHEDULING COMPONENT
NOTE: This related information is not an official part of SEMI E105. This related information was approved for publication by
full letter ballot procedures on August 28, 2000.
NOTE: This related information is included with the Scheduling Component specification to aid the readers in understanding the
intent and use of the standard.
R1-1 The Scheduling Component has two types of interfaces:
A. Scheduling and Dispatching Service Interface - this is the interface for services provided by the Scheduling
Component in response to requests from the Factory Operations Component or some other client. It also
includes interfaces to support asynchronous actions for an active scheduler or dispatcher which provides the
same information content on an event driven basis rather than requiring a client request.
This is included within the scope of the current standard.
B. Scheduling and Dispatching Factory Input Interface - this is the interface used by other components to provide
updated information on factory state used by the Scheduling Component in making scheduling and dispatching
decisions. The updates are typically provided by other CIM Framework components to the Scheduling
Component asynchronously.
This is NOT included within the scope of the current standard.
R1-2 The goal for CIM Framework standards is to eventually standardize both of these types of interface. However,
at this time there are two major issues that prevent inclusion of the Factory Input Interface to the Scheduling
Component.
1. There is inadequate consensus on the technical maturity of the currently available asynchronous input
mechanisms. While the CIM Framework specifies events for delivery via an Event Broker mechanism, it is not
assumed that the quality of service for events will include guaranteed delivery and performance adequate for
keeping a Scheduling Component current with real-time factory state changes. For a more complete discussion
of the CIM Framework technical architecture issues, see SEMI E96.
2. Some key components of the CIM Framework needed to provide factory state to the Scheduling Component
have not yet been approved as SEMI standards.
R1-3 The following approach is suggested as a possible way to address Scheduling Component Input in the future:
1. Identify the most important inputs required by the Scheduling Component in a follow-on ballot for the
Scheduling Component to be used during the interim period until the full component specifications containing
those events are approved as SEMI standards.
2. Suppliers who implement the Scheduling Component should take advantage of existing standard interfaces
defined in adopted CIM framework standards and use this experience as expert input on future updates to this
standard.
3. Encourage technical studies to provide added understanding of the tradeoffs and limitations that impact
standardization of this interface in the future.