 |
| Purchase Information |
| Use this form to request purchase information on SEMI online subscriptions. |
|
|
Document SEMI E96 is offered by IHS as part of an online subscription. This subscription contains many documents on the same topic.
You may also purchase this document alone from the IHS Standards Store.
SEMI E96 Document Information:
Title
GUIDE FOR CIM FRAMEWORK TECHNICAL ARCHITECTURE
Semiconductor Equipment and Materials International
Publication Date:
Nov 1, 2001
Scope:
Intended Audience
This document is intended for developers of components and
applications, and integrators of MES systems that adhere to the CIM
Framework specifications. It is also intended for system architects
who contribute to the evolution of the CIM Framework architecture
and guides based on implementation experience. A guide for
technical architecture is focused on the software technologies that
support the architectural goals for the CIM Framework rather than
on the manufacturing domain concepts that the CIM Framework
encompasses. The technical architecture perspective complements
SEMI E81.
Architectural Issues Not Covered
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.
Persistence
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.
System Performance
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 implementation dependent mechanism.
Data Replication
Data replication is a technique used to provide additional fault
tolerance or improve system performance in certain situations. The
CIM Framework excludes specification of replication strategies as
an implementation dependent mechanism.
Change Management
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.
Externalization
Externalization can be used to provide a form of persistence or
to transfer object state between disjoint implementations. The
ability of an object to externalize 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.
NOTICE: 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 or other limitations prior to use.
Purpose
This guide describes technical architecture choices that enable
application components to cooperate in a Computer Integrated
Manufacturing (CIM) environment and reduce the effort required to
integrate those components into a working solution. The CIM
Framework technical architecture guide builds on publicly available
specifications for distributed object computing. 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 underlying
distributed object communication infrastructure.
This guide provides guidance for the technical foundation of the
SEMI Computer Integrated Manufacturing (CIM) Framework standards.
It discusses a component-based architecture using object-oriented
and framework technology that helps implementers achieve component
interoperability and substitutability, application extensibility,
and reuse. It establishes the role of distributed object
communications infrastructure in providing 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. However, these
mappings are not intended to be prescriptive. Further work may be
required to define additional mappings to emerging technologies.
Many implementation issues that should be resolved for a particular
software implementation are outside the scope of this guide.
Adhering to this guide for technical architecture alone does not
provide interoperability between applications. 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 environments 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 Framework Domain
Architecture is also required for interoperability of domain
components.
• More complete semantics (including behavioral constraints and
collaboration patterns) for components are needed to ensure
consistent interactions among components developed by separate
suppliers.
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
technical architecture identifies those crucial technical
requirements that should be considered by both CIM software
suppliers and consumers. The proposed standard identifies the
technical capabilities implementations 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.
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 Framework components. These areas are:
• Distributed Object Communication — Provides the basic
services to enable implementations supporting the CIM Framework
interfaces to transparently locate other, possibly distributed
implementations 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 implementations 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.
• Event Specification — Establishes the delivery
mechanism, identification conventions, and data structures for
reporting the occurrence of anticipated 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.
About IHS
IHS (NYSE: IHS) is a leading global provider of critical technical information, decision-support tools and related services in a number of industries including aerospace and defense, automotive, construction, electronics, and energy. IHS serves customers ranging from large governments and multinational corporations to smaller companies and technical professionals in more than 100 countries. IHS been in business for more than 45 years and employ more than 2,300 people around the world.
