semi合集-English.pdf - 第2682页

SEMI E97-0200A © SEMI 2000 2 These extensions will be addressed before upgrade to full sta ndard stat us. 3.1.6 The in terfaces specified f or M E S Factor y, Area, and Compon e ntManager are included in the E81 responsi…

SEMI E97-0200A © SEMI 20001

SEMI E97-0200A

PROVISIONAL SPECIFICATION FOR CIM FRAMEWORK GLOBAL

DECLARATIONS AND ABSTRACT INTERFACES

This provisional specification was technically approved by the Global Information and Control Committee

and is the direct responsibility of the North American Information and Control Committee. Current edition

approved by the North American Regional Standards Committee on October 21 and December 15, 1999.

Initially available at www.semi.org January 2000; to be published February 2000.

NOTE: This document was published twice during the

February 2000 (0200) publishing cycle.

1 Purpose

1.1 This document defines the global declarations used

by all other components of the CIM Framework and

also specifies the common architecture patterns that

serve to functionally integrate CIM Framework

components. The material architecture defines

functionality common to product management, durables

management and consumables management

components. The factory resource architecture defines

relationships and common functionality of a variety of

factory resources. The job architecture defines a

factory-wide model for controlling factory jobs that

drive a variety of manufacturing tasks. These

specifications are separated into a distinct group to

enable them to be specified once and then logically

included or inherited wherever they are subsequently

needed.

2 Scope

2.1 This specification provides the common interfaces

required by Manufacturing Execution Systems to:

• Provide type definitions for common data

structures to ensure consistent representation.

These items include data types for common

concepts such as coordinates, priorities,

timestamps, and sequences of basic data types.

• Provide definitions for common exceptions used

consistently throughout the CIM Framework.

• Provide the material architecture interfaces

common to identifying, grouping, moving, locating

and tracking material in the factory.

• Provide the factory resource architecture interfaces

common to defining, organizing, tracking usage of

and maintaining factory resources including

equipment, sensors, durables, and people.

• Provide the job architecture interfaces common to

creating, executing and managing work in the

factory. The job architecture is specialized for

material processing jobs, material transport jobs,

resource maintenance jobs and factory jobs that

drive product material through their process flows.

2.2 This standard does not purport to address safety

issues, if any, associated with its use. It is the

responsibility of the users of this standard to establish

appropriate safety and health practices and determine

the applicability of regulatory limitations prior to use.

3 Limitations

3.1 Provisional Status

3.1.1 This specification is designated as provisional

due to known areas that need to be completed. The

following items summarize the deficiencies of the

provisional specification to be addressed before a

subsequent ballot to upgrade it to full standard status.

3.1.2 The specification uses the IDL typedef “any” in

several places. While this usage provides flexibility, it

can have the effect of reducing interoperability due to

differences in interpretation of the value provided by

separate implementations that interact through a

standard interface. The “any” typedefs should be

replaced with explicit data types prior to upgrade from

Provisional to full Standard status.

3.1.3 The definition of interfaces for retrieval of

history associated with CIM Framework objects may

need to be added to abstract interfaces in this document

after the complete specification for the history facility

within the CIM Framework Factory Services

Component.

3.1.4 The specification of CIM Framework states

reported through published state change events is

currently based on a type definition for an enumeration

of state values. There may be alternate representations

for states that are better able to capture the semantics of

nested and parallel states. The state representation used

for the CIM Framework will be reviewed and possibly

changed before upgrade to full standard status.

3.1.5 The Resource model defined in SEMI E81

includes several extensions that are not yet included in

this specification. These extensions include

composition of resources from other resources,

capabilities associated with resources, and associations

with tracking and maintenance functions for resources.

SEMI E97-0200A © SEMI 2000 2

These extensions will be addressed before upgrade to

full standard status.

3.1.6 The interfaces specified for MESFactory, Area,

and ComponentManager are included in the E81

responsibilities for the Factory Component within

Factory Operations. These interfaces will need to be

moved to that component when it is considered in a

future ballot.

4 Referenced Standards

4.1 SEMI Standards

SEMI E5 — SEMI Equipment Communications

Standard 2 Message Content (SECS-II)

SEMI E10 — Standard for Definition and

Measurement of Equipment Reliability, Availability,

and Maintainability (RAM)

SEMI E81 — Provisional Specification for CIM

Framework Domain Architecture

4.2 Other Standards

UML Notation Guide, Version 1.1, document number

ad/97-08-05, Object Management Group

ISO/IEC International Standard 14750 (also ITU-T

Recommendation X.920) –– Information Technology –

Open Distributed Processing – Interface Definition

Language

NOTE 1: As listed or revised, all documents cited shall be the

latest publications of adopted standards.

5 Terminology

5.1 abstract interface — an interface specified only

for inheritance rather than for implementation in order

to standardize common features shared by all

specializations of the interface.

6 Requirements

6.1 Global Type Definitions

6.1.1 This section describes data type definitions and

exceptions that are global in nature. By “global” it is

meant that they are designed to be used by any

component within the CIM Framework. This

specification does not address how they are

implemented within a CIM Framework conformant

1 UML Notation Guide v1.1 is available to the general public at

http://www.omg.org/cgi-bin/doclist.pl, +1-508-820 4300, Object

Management Group, Inc. , Framingham Corporate Center, 492 Old

Connecticut Path, Framingham, MA 01701.

2 ISO Central Secretariat, 1, rue de Varembé, Case postale 56, CH-

1211 Genève 20, Switzerland

application; that level of detail is within the realm of the

development effort.

6.1.2 Global type definitions are specified as IDL

declarations which may be referenced by any CIM

Framework interface. The CIM Framework uses the

keyword typedef 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). The keyword struct

begins the type declaration for record structures

composed of a collection of named and typed values.

The third form of type definition is an enumerated type

beginning with the reserved word enum. Enumerated

types are used to declare a list of tokens that can be

used as values of that type. Enumerated types are

mainly used to denote the states of an object for

communication in CIM Framework events. Finally,

collections of values are declared with the keyword

sequence. This kind of type definition may or may not

imply significance to the ordering of the members in

the sequence. Where no ordering constraint is

mentioned, the elements of the sequence are not

assumed to be in any meaningful order.

NOTE 2: In the following definitions, “//” or “/* .... */”

delimits a comment.

NOTE TO THE READER: The comments in the following

sections (described in NOTE 2, above) appear to immediately

precede, rather than follow, the items they discuss. — SEMI

Staff

6.1.3 All CIM Framework specifications will be

declared within the context of the CIMFW module

which spans all of the components of the CIM

Framework. Within the CIMFW module, the global

type definitions will be declared within a second-level

module called Global.

Module: Global

typedef string Identifier;

typedef unsigned long Flags;

struct NamedValue {

Identifier name;

any argument;

long len;

Flags arg_modes;

};

typedef NamedValue NameValue;

typedef sequence <NamedValue> NameValueSequence;

typedef string PropertyName;

struct Property {

PropertyName property_name;

any property_value;

};

typedef sequence <Property> Properties;

/* This type definition represents units for factory parameters, measurements. etc., and conforms to the SEMI E5

standard for representation of units. In that standard, the string contains a code representing a value of the units. For

example, “ns” would mean nano-seconds; “A” for ampere; and “wfr” for wafer. */

typedef string Unit;

typedef string Units;

/* This type definition represents a sequence of string values. */

typedef sequence <string> StringSequence;

/* This type definition represents a sequence of any values. */

typedef sequence <any> AnySequence;

/* This type definition represents a sequence of long values. */

typedef sequence <long> LongSequence;

/* This enumerated type identifies event priorities and is used in each event definition. */

enum PriorityOfEvent {

Low,

Medium,

High,

Alarm };

/* This enumerated type identifies the lifecycle states that an object may go through. It is used in event notifications

of state changes. */