semi合集-English.pdf - 第2404页

SEMI E86-0200 © SEMI 1999 , 2000 4 interface Resource : OwnedEntity { }; interface ComponentManager : Resource { }; interface Job { }; 6.2.3 O ther CIM Framework Inter fa c e s 6.2.3.1 T his section identifies interf ac …

100%1 / 7923
SEMI E86-0200 © SEMI 1999, 20003
4 Referenced Standards
4.1 SEMI Standard
SEMI E81 — Provisional Specification for CIM Framework Domain Architecture
4.2 ISO/IEC Standard
1
ISO/IEC 14750 (also ITU-T Recommendation X.920) — Information Technology – Open Distributed Processing –
Interface Definition Language
4.3 OMG Standard
2
UML Notation Guide, Version 1.1, document number ad/97-08-05
NOTE: As listed or revised, all documents cited shall be the latest publications of adopted standards.
5 Terminology
5.1 person — personnel performin g manufacturing operations within a factory.
5.2 person responsibility — the concept of “responsibility” implies that factory personnel are authorized to
perform, operate or access a specific factory object (but it does not imply ownership).
5.3 skill — skill is an attribute of factory personnel denoting that they are qualified to assist a process resource or
job in the performance of a process capability or some other factory operation.
5.4 skill qualification — a skill qualification indicates that factory personnel meet a requirement (or all
requirements) necessary to perform some factory operation.
5.5 skill requirement — a skill requirement is the training or medical examination(s) required to achieve a specific
skill.
6 Requirements
6.1 The following sections provide the specification of interfaces that comprise the Factory Labor Component. The
model notation used is the Unified Modeling Language (UML). UML is documented in the UML Notation Guide.
The details of each interface are supplied using standard IT-ODP-IDL. Conformant implementations of the Factory
Labor Component shall provide support for all elements of the IDL specifications and the semantics provided in the
UML models. Conformant implementations are not constrained to any specific implementation approach, provided
that a mapping is provided to the IDL specification.
6.2 External Interfaces, Global Type Definitions, Global Exceptions and Events
6.2.1 The following interfaces (external to this component), global type definitions, global exceptions, and events
are required to support the Factory Labor component specification.
6.2.2 Abstract and Base Interfaces
6.2.2.1 Base interfaces provide a suite of interfaces that are used throughout the CIM Framework Specification.
The Abstract Interfaces provide a hierarchy of abstract interfaces that are used as “Inherited Interfaces” in the rest of
the framework. These interfaces are expected to be specialized in a specific implementation.
6.2.2.2 This section identifies base and abstract interfaces required by the Factory Labor component specification.
interface NamedEntity {
};
interface OwnedEntity : NamedEntity {
};
1 ISO Central Secretariat, 1, rue de Varembé, Case postale 56, CH-1211 Genève 20, Switzerland
2 Object Management Group, Inc., Framingham Corporate Center, 492 Old Connecticut Path, Framingham, MA 01701, 1.508.820.4300,
http://www.omg.org/cgi-bin/doclist.pl
SEMI E86-0200 © SEMI 1999, 2000 4
interface Resource : OwnedEntity {
};
interface ComponentManager : Resource {
};
interface Job {
};
6.2.3 Other CIM Framework Interfaces
6.2.3.1 This section identifies interfaces within other CIM Framework components that are needed to satisfy
relationships with the Factory Labor component.
interface HistoryCollection { // from Factory Services
};
interface History { // from Factory Services
};
interface MESFactory { // from Factory Management
};
6.2.4 Global Type Definitions
6.2.4.1 The CIM Framework uses IT-ODP-IDL typedefs in two ways:
• To define aliases for compound object types (structs), which can then be used in IDL specifications and
• To define aliases for basic object types, but with additional implied semantics. (e.g., the units typedef defines a
string, whose contents conform to definitions found in SEMI E5).
6.2.4.2 This section identifies the global type definitions required by the Factory Labor component specification.
typedef sequence<string> stringSequence ;
typedef struct HistoryEvent_body {
string subject ;
} HistoryEvent ;
struct ulonglong {
unsigned long low ;
unsigned long high ;
};
typedef ulonglong TimeT ;
typedef TimeT TimeStamp ;
struct IntervalT {
TimeT lower_bound ;
TimeT upper_bound ;
};
SEMI E86-0200 © SEMI 1999, 20005
typedef IntervalT TimeWindow ;
typedef struct Shift_Structure {
string name ;
// ...
} Shift ;
typedef struct PersonResponsibilitystruct {
string responsibilityCategory ;
any responsibility ;
} PersonResponsibility;
typedef sequence<ProcessCapability> ProcessCapabilitySequence ;
typedef stringSequence CategorySequence ;
typedef sequence<HistoryEvent> HistoryEventSequence ;
typedef sequence<Job> JobSequence ;
typedef sequence<Machine> MachineSequence ;
typedef sequence<Person> PersonSequence ;
typedef sequence<QualificationData> QualificationDataSequence ;
typedef sequence<Resource> ResourceSequence ;
typedef sequence<SkillRequirement> RequirementSequence ;
typedef sequence<PersonResponsibility> ResponsibilitySequence ;
typedef sequence<Skill> SkillSequence ;
typedef string PropertyName;
struct Property
{
PropertyName property_name;
any property_value;
};
typedef sequence<Property> Properties;
6.2.5 Global Exception Declarations
6.2.5.1 An exception is an infrastructure mechanism used to notify a calling client of an operation that an unusual
condition occurred in carrying out the operation. This section identifies the global exception declarations required by
the Factory Labor component specification.
exception FrameworkErrorSignal {
unsigned long errorCode ;
any errorInformation ;
};
exception InvalidStateTransitionSignal {
};
exception SetValueOutOfRangeSignal {
};
6.2.6 Events
6.2.6.1 An event is an asynchronous message denoting the occurrence of some incident of importance. For
example, state change or new object created. This section identifies the events defined by the Factory Labor
component specification. Note that “//” or “/* ....*/” infers a comment.