semi合集-English.pdf - 第2661页

SEMI E96-1101 © SEMI 1999 , 2001 1 SEMI E96-1101 GUIDE FOR CIM FRAMEWORK TECHNICAL ARCHITECTURE This g u ide w as technica lly appr oved by the Global Inf ormation and Control C omm ittee and is the direc t responsi bili…

SEMI E95-1101 © SEMI 2000, 200115

7 Related Documents

7.1 SEMATECH Documents

Computer Integrated Manufacturing (CIM) Application

Framework Specification

SCC User-Interface Style Guide

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.

1 SEMATECH, 2706 Montopolis Drive, Austin, TX, 78741-6499.

Website: www.sematech.org

International), 3081 Zanker Road, San Jose, CA 95134. Reproduction o

the contents in whole or in part is forbidden without express written

consent of SEMI.

SEMI E96-1101 © SEMI 1999, 20011

SEMI E96-1101

GUIDE FOR CIM FRAMEWORK TECHNICAL ARCHITECTURE

This guide 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

European Regional Standards Committee on June 11, 2001, and by the North American Regional Standards

Committee on July 19, 2001. Initially available at www.semi.org August 2001; to be published November

2001. Originally published February 2000. This document replaces PR5-0699 in its entirety.

1 Purpose

1.1 This guide describes technical architecture choices

that enable application components to cooperate in a

Computer Integrated Manufacturing (CIM) environ-

ment and reduce the effort required to integrate those

components into a working solution. The CIM Frame-

work technical architecture guide builds on publicly

available specifications for distributed object comput-

ing. It defines manufacturing production systems

requirements for the technical infrastructure needed for

improved component interoperability, substitutability,

and extensibility. It provides guidance for specifying

components and addresses options for using an under-

lying distributed object communication infrastructure.

1.2 This guide provides guidance for the technical

foundation of the SEMI Computer Integrated Manufact-

uring (CIM) Framework standards. It discusses a com-

ponent-based architecture using object-oriented and

framework technology that helps implementers achieve

component interoperability and substitutability, applica-

tion extensibility, and reuse. It establishes the role of

distributed object communications infrastructure in pro-

viding necessary support for the framework technology.

Specification methods for mapping a CIM Framework

specification to alternative infrastructure technologies

are also addressed by this technical architecture. How-

ever, these mappings are not intended to be prescrip-

tive. Further work may be required to define additional

mappings to emerging technologies. Many implement-

ation issues that should be resolved for a particular

software implementation are outside the scope of this

guide.

1.3 Adhering to this guide for technical architecture

alone does not provide interoperability between appli-

cations. While the technical architecture provides a

foundation for interoperability, it is limited by the

following factors:

• Multiple infrastructure implementation choices are

possible, and interoperability across these environ-

ments is not guaranteed.

• The technical architecture intentionally limits its

scope to only the most fundamental infrastructure

requirements, leaving additional technical issues

for future guide upgrades or for implementers’

discretion.

• Conformance to a specification for CIM Frame-

work Domain Architecture is also required for

interoperability of domain components.

• More complete semantics (including behavioral

constraints and collaboration patterns) for compo-

nents are needed to ensure consistent interactions

among components developed by separate

suppliers.

1.4 A guide for technical architecture is a necessary,

but not a sufficient, basis to achieve the goals of the

CIM Framework specifications. It does not mandate

specific solutions to address the identified technical

requirements because there are multiple implementation

choices that meet these requirements. Rather, the tech-

nical architecture identifies those crucial technical

requirements that should be considered by both CIM

software suppliers and consumers. The proposed stan-

dard identifies the technical capabilities implement-

ations should provide, but leaves the implementation

options open. It is the responsibility of suppliers to

provide and explain an implementation of each

capability, and the responsibility of consumers to assess

particular implementations for use in their factories.

1.5 This guide provides guidance on the technical

tradeoffs for services provided by the distributed

computing infrastructure for the purpose of supporting

and enabling the domain specifications of CIM Frame-

work components. These areas are:

• Distributed Object Communication — Provides the

basic services to enable implementations

supporting the CIM Framework interfaces to trans-

parently locate other, possibly distributed imple-

mentations and exchange messages requesting

standard CIM Framework operations. Interface

Definition Language provides a formal specifica-

tion of the CIM Framework interfaces that can be

automatically transformed into conformant imple-

mentations ready for integration and interoperation.

• Exception Declarations — Identify the form and

structure of return messages that inform requestors

that a requested operation resulted in an

anticipated, but abnormal outcome.

SEMI E96-1101 © SEMI 1999, 2001 2

• Event Specification — Establishes the delivery

mechanism, identification conventions, and data

structures for reporting the occurrence of antici-

pated state changes to CIM Framework objects.

• Distributed Transactions — Define mechanisms

needed to coordinate the start, completion or

rollback of units-of-work that cross CIM

Framework component boundaries.

• Component Manager Support — Identifies the

component-level operations needed to create,

locate, or remove instances of objects (and manage

collections of those objects) that support the CIM

Framework specified interfaces.

2 Scope

2.1 Intended Audience

2.1.1 This document is intended for developers of

components and applications, and integrators of MES

systems that adhere to the CIM Framework speci-

fications. It is also intended for system architects who

contribute to the evolution of the CIM Framework

architecture and guides based on implementation exper-

ience. A guide for technical architecture is focused on

the software technologies that support the architectural

goals for the CIM Framework rather than on the manu-

facturing domain concepts that the CIM Framework

encompasses. The technical architecture perspective

complements SEMI E81.

2.2 Architectural Issues Not Covered

2.2.1 A number of architectural issues are not covered

within this document because they are beyond the scope

of the CIM Framework standards and are not expected

to come within the scope of the standards as they are

revised. They are itemized here because a product

architecture layered on the CIM Framework Technical

Architecture should address these additional

architecture issues. In these cases, other more general

specifications emerging in the infrastructure technology

areas are expected to provide these needed standards.

The CIM Framework domain specifications do not

require specific conformance in these areas to support

component specifications.

2.2.2 Persistence

2.2.2.1 Persistence refers to the ability of an object to

maintain a nonvolatile copy of its current state such that

the object could recreate the state during a future

initialization. There are various operations for object

persistence, and problems can occur if objects with

cross-references do not coordinate their persistence

strategies and mechanisms. The CIM Framework

excludes persistence as an implementation mechanism.

2.2.3 System Performance

2.2.3.1 System performance is highly dependent on the

selection of hardware and software platforms for

system execution. Tests should be performed to verify

adequate system performance and scalability for the

anticipated operating environment. Performance tuning

mechanisms or measurement tools are excluded from

the CIM Framework specifications as an implement-

ation dependent mechanism.

2.2.4 Data Replication

2.2.4.1 Data replication is a technique used to provide

additional fault tolerance or improve system perform-

ance in certain situations. The CIM Framework

excludes specification of replication strategies as an

implementation dependent mechanism.

2.2.5 Change Management

2.2.5.1 Change management is the ability to introduce

and control changes to the system configuration. The

CIM Framework encompasses change management in

the domain context of document control, but the CIM

Framework excludes the broader treatment of change

management for the MES software configuration itself.

2.2.6 Externalization

2.2.6.1 Externalization can be used to provide a form

of persistence or to transfer object state between dis-

joint implementations. The ability of an object to exter-

nalize its data and state supports recovery of data and

state for objects that terminated from memory. The

CIM Framework excludes externalization as an

implementation dependent mechanism.

2.3 This standard does not purport to address safety

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

bility of the users of this standard to establish appro-

priate safety and health practices and determine the

applicability of regulatory limitations prior to use.

3 Limitations

3.1 The CIM Framework should continue to evolve to

meet the needs of a competitive and vital industry. The

content of this framework represents a significant

amount of real development experience from a number

of commercial software suppliers and their customers.

These specifications reflect the product architectures of

those companies, as well as the requirements of their

customers. This evolution process should continue as

more products based on the CIM Framework are

developed.

3.1.1 This guide acknowledges the following

deficiencies that should be addressed in future

revisions. These deficiencies are identified in the

following sections.