CIMOSA: CONCEPTS AND
APPLICATION
Vijay Ravichandran
Masters of Science Graduate Student
Submitted in Partial Completion of the Requirements of
IEM 5303
Advanced Manufacturing Systems Design
FALL’ 99
This paper was developed to assist students in partial fulfillment of course
requirements. No warranty of any kind is expressed or implied. Readers of this
document bear sole responsibility for verification of its contents and assume any/all
liabilty for any/all damage or loss resulting from its use.
Table of Contents
1.0
ABSTRACT ........................................................................................................... 1
2.0
INTRODUCTION................................................................................................. 1
3.0
ENTERPRISE INTEGRATION ......................................................................... 2
LEVELS OF INTEGRATION ................................................................................................ 2
4.0
ENTERPRISE MODELING ............................................................................... 3
5.0
CIMOSA OVERVIEW ........................................................................................ 4
6.0
CIMOSA REFERENCE ARCHITECTURE ..................................................... 4
CIMOSA ARCHITECTURAL PRINCIPLES ............................................................................. 5
THE CIMOSA MODELING FRAMEWORK ............................................................................ 5
CIMOSA BUSINESS MODELING CONSTRUCTS ................................................................... 6
7.0
CIMOSA PROCESS BASED ENTERPRISE MODELING ............................ 7
8.0
CIMOSA INTEGRATING INFRASTRUCTURE .......................................... 10
9.0
CIMOSA MODELING AND THE SYSTEM LIFE CYCLE ........................ 11
CIMOSA ENTERPRISE SYSTEM LIFE CYCLE .................................................................... 12
10.0
CIMOSA DOMAINS .......................................................................................... 13
REQUIREMENTS DEFINITION MODELING ........................................................................ 15
DOMAIN ESTABLISHMENT.............................................................................................. 16
11.0
SUMMARY AND CONCLUSION ................................................................... 16
BIBLIOGRAPHY ........................................................................................................... 17
Page i
List of Figures
FIGURE 1. LEVELS OF INTEGRATION [7] ........................................................................................ 2
FIGURE 2. THE CIMOSA MODELING FRAMEWORK [5]....................................................................... 4
FIGURE 3. CIMOSA BUSINESS MODELING CONSTRUCTS [2] ............................................................... 6
FIGURE 4. DOMAINS WITH INTERACTING DOMAIN PROCESSES [2] .................................................. 7
FIGURE 5. DECOMPOSITION OF A DOMAIN PROCESS [2] ................................................................ 8
FIGURE 6. DOMAIN PROCESSES REPRESENTED AS A NETWORK OF ENTERPRISE ACTIVITIES [2] ............ 8
FIGURE 7. FUNCTIONAL OPERATIONS EXECUTED BY FUNCTIONAL ENTITIES [2] ................................. 9
FIGURE 8. INTEGRATING INFRASTRUCTURE [9] ............................................................................. 10
FIGURE 9. CIMOSA MODELING AND ENTERPRISE SYSTEM LIFE CYCLE [2] ......................................... 11
FIGURE 10. CIMOSA CONCEPT AND APPLICATION [9] .................................................................... 12
FIGURE 11. CIMOSA AND NON-CIMOSA DOMAINS [3] .................................................................... 13
FIGURE 12. DOMAIN PROCESSES [3] ........................................................................................... 14
FIGURE 13. FIRST LEVEL OF DECOMPOSITION – REQUIREMENTS DEFINITION [3] ................................. 15
FIGURE 14. SECOND LEVEL OF DECOMPOSITION – DOMAIN ESTABLISHMENT [3] ................................ 16
Page ii
1.0 ABSTRACT
Integrating and managing complex enterprises requires understanding, partitioning and
simplification of the complexity. Enterprise modeling supports these requirements by
providing means for describing process oriented systems and decomposing them into
manageable parts. The paper describes the CIMOSA (Open System Architecture For
Computer Integrated Manufacturing) concept, the enterprise modeling solution for
identification of available information and its use in the operational processes of the
manufacturing enterprise.
The CIMOSA Business Modeling Process follows the enterprise system life cycle
starting with the requirements definition, followed by design specification and ending
with the description of the implemented operational system. In addition to this top-down
approach, bottom-up and iterative modeling are supported as well. CIMOSA models may
be used not only in decision support for evaluation of alternative solutions in enterprise
operations, but also for directly driving operation control and monitoring. Therefore,
enterprise modeling is complimented by an Integrating Infrastructure, which supports the
execution of enterprise models.
KEYWORDS: Enterprise Integration, Enterprise Modeling, Business Process Modeling,
System life cycle, CIMOSA, CIM, Open System Architecture
2.0 INTRODUCTION
Enterprise modeling is a prerequisite for successful enterprise integration. CIM should
provide the industry opportunities to streamline production flows, reduce lead times and
increase overall quality while adapting the enterprise fully to market needs. CIMOSA
(Open System Architecture For CIM) provides a widely accepted CIM concept with an
adequate set of architectural constructs to structure CIM systems. The primary objective
of CIMOSA is to provide a framework for analyzing the enterprise requirements and
translating them into a system, which enables and integrates the functions that match the
requirements. The paper describes the CIMOSA concept, the enterprise modeling
Page 1
solution for identification of available information and its use in the operation of a
manufacturing enterprise.
3.0 ENTERPRISE INTEGRATION
“CIM is the integration of the total manufacturing enterprise through the use of
integrated systems and data communications coupled with managerial philosophies
that improve organizational and personnel efficiency” [1].
The concept of Enterprise Integration (EI) is a response to the traditional “islands-ofautomation’ view of CIM. EI is much broader than factory automation integration; it is
the integration of people, technology, and the business process throughout the enterprise
[8]. EI is an ongoing process rather than a one-time effort. The enterprise will evolve
over time according to both internal needs and external changes and opportunities.
LEVELS OF INTEGRATION
FIGURE 1. LEVELS OF INTEGRATION [7]
Three levels of integration, physical systems integration, applications integration, and
business integration can be identified [7]. Physical Systems Integration is concerned with
the interconnection of manufacturing automation and data processing facilities, e.g.
between CAD, CAM, PPS, and the manufacturing cells to permit the interchange of
information between the so-called ‘islands-of-automation’ [8]. Application Integration is
concerned with the control and integration of applications in the data processing sense,
Page 2
which means interoperability between applications and users and supply and removal of
information through inter and intra system communication.
Business Integration is concerned with integrating those functions, which manage,
control, and monitor business processes. Functions, which provide supervisory control of
the operational process and in-turn, coordinate the day-to-day execution of activities at
the application level. Modeling business processes and their interrelations and its use for
decision and operational support is key to business integration [7].
EI has to encompass all these levels of integration, with emphasis on Business
Integration. Only with a focus on the business needs rather than on application or system
needs, can all the different aspects of enterprise operation be identified which have to be
considered in the course of modifying and optimizing the operation [7].
4.0 ENTERPRISE MODELING
Modeling means formalizing knowledge in an unambiguous form, making it possible to
be exploited by other enterprise agents, human beings, and software applications [8]. A
model identifies the different processes in the enterprise, and contains the machines,
information, transfer of information, human involvement, and functions that have to be
carried out.
Enterprise modeling has to fulfill several requirements to achieve effective and
efficient enterprise integration [8]:

Provide a modeling language easily understood by non-IT professionals, but
sufficient for modeling complex industrial environments.

Provide a modeling framework which:
-
Covers the life cycle of enterprise operation from requirements definition
to end of life cycle.
Enables focus on different aspects of enterprise operation by hiding those
parts of the model not relevant for the particular point of view.
-
Supports re-usability of models or model parts
-
Allows application of different modeling methodologies to accommodate
different modeling needs.

Support graceful migration through an evolutionary approach enterprise
modeling, coexisting with legacy systems.
Page 3
5.0 CIMOSA OVERVIEW
CIMOSA (Open System Architecture For CIM) is an ESPIRIT1 supported pre-normative
development aimed at process-based enterprise modeling and application of these models
in the control and monitoring of enterprise operations [2].
1
The Reference Architecture supports the description of the enterprise, in all its
functions, from the management level to the shop floor level. CIMOSA consists of an
Enterprise Modeling Framework and an Integrating Infrastructure. The CIMOSA concept
has been evaluated and verified by other ESPIRIT projects, professional societies,
independent organizations in many countries, and by AMICE2 member organizations [2].
CIMOSA enterprise models may be used not only in decision support for engineering and
evaluating enterprise operation alternatives, but also in model driven operation
monitoring and control.
6.0 CIMOSA REFERENCE ARCHITECTURE
FIGURE 2. THE CIMOSA MODELING FRAMEWORK [5]
The modeling framework shown in figure 2 structures the CIMOSA Reference
Architecture into a partial level and a generic level, with each level supporting different
views on the particular enterprise model. The concept of views allows working with a
1
European Strategic Programme for Research and Development in Information Technology.
2
European CIM Architecture (in reverse)
Page 4
subset of the model, providing especially the business user with a reduced complexity for
his particular area of interest [2]. CIMOSA has defined four different modeling views;
Function, Information, Resource, and Organization. But, this set of views can be
extended [2], [9].
The CIMOSA Reference Architecture supports modeling of the complete life cycle of
enterprise
operations;
Requirements
Definition,
Design
Specification,
and
Implementation Description.
CIMOSA ARCHITECTURAL PRINCIPLES
The CIMOSA architectural principles are based on the generalized concept of isolation
[7]:

Isolation between the User representation and the System representation: which
restricts the impact of changes and provides the ability to modify the enterprise
behavior in order to cope with organizational changes.

Isolation between Control and Functions: which makes it possible to revise the
enterprise behavior, in order to meet changing circumstances without altering the
installed functionality.

Isolation between Functions and Information: to felicitate integration,
application portability, inter-operability, and maintainability.
THE CIMOSA MODELING FRAMEWORK
The CIMOSA modeling framework (CIMOSA cube) is based on [7]:

Three Architectural Levels
Generic Level
Catalogue for basic building blocks
Partial Level
Library of partial models applicable to particular purposes
Particular
Model of a particular enterprise built from building blocks and partial
Level
models.
Page 5

Three Modeling Levels
Requirements
For gathering business requirements
Business
User
Modeling
Design
For
specifying
optimized
and
system-oriented System
Modeling
representation of the business requirements
Designer
Implementation For describing a complete CIM system and all its System
Modeling

implemented components
Developer
Four Integrated Views
Function
For describing the expected behavior and functionality of the enterprise
View
Information
For describing the integrated information objects of the enterprise
View
Resource View For describing the resource objects of the enterprise
Organization
For describing the organization of the enterprise
View
CIMOSA BUSINESS MODELING CONSTRUCTS
FIGURE 3. CIMOSA BUSINESS MODELING CONSTRUCTS [2]
Page 6
Enterprise operation should not be modeled as a large model but rather as a set of
cooperating processes. The CIMOSA Reference Architecture allows different users to
model different areas of the enterprise but provides the integrity of the overall model [2].
The basic set of common building blocks for business modeling is shown in figure 3.
Processes, Events, and Enterprise Activities are the Object classes that describe
functionality and behavior (dynamics) of the enterprise operation. Inputs and outputs of
Enterprise Activities define the information (Enterprise Object) and resources needed.
Organizational aspects are defined in terms of responsibilities and authorization
(Organizational Elements) for functionalities, information, resources, and organization.
They are structured in Organizational Units or Cells. CIMOSA employs the objectoriented concepts of inheritance, structuring its constructs into a hierarchy of object
classes [2], [9].
7.0 CIMOSA PROCESS BASED ENTERPRISE MODELING
FIGURE 4. DOMAINS WITH INTERACTING DOMAIN PROCESSES [2]
Three enterprise Domains are shown in figure 4, DM1, DM2, and DM3, each of these
domains is represented by its functionality – a set of Domain Processes. Domain
processes communicate with each other through Events and Results.
Page 7
FIGURE 5. DECOMPOSITION OF A DOMAIN PROCESS [2]
The decomposition of the Domain Processes (DP 2.1) via Business Processes leads to the
identification of Enterprise Activities, as shown in figure 5.
FIGURE 6. DOMAIN PROCESSES REPRESENTED AS A NETWORK OF ENTERPRISE ACTIVITIES [2]
The connecting control flow represented by a set of Behavioral Rules, is as shown in
figure 6. The network of these activities is the functional and dynamic representation of
the Domain process DP 2.1 [2]. Event1 and Event2 trigger the Enterprise Activities EA1
and EA2. Result ‘a’ and Result ‘b’, which relate to the Domain Process DP 2.1, are
produced by EA3 and EA5 respectively.
Page 8
FIGURE 7. FUNCTIONAL OPERATIONS EXECUTED BY FUNCTIONAL ENTITIES [2]
At the systems design level, the Enterprise Activities are further decomposed into
Functional Operations, as shown in figure 7 (A). These Functional Operations are defined
with relation to their executing resource types, the Functional Entities. Each Functional
Operation will be completely executed by one Functional Entity, but a Functional Entity
is capable of executing more than one Functional Operation, as shown in figure 7 (B) [9].
Functional Entities are resources, which are capable of receiving, sending, processing,
and storing information [9].
Page 9
8.0 CIMOSA INTEGRATING INFRASTRUCTURE
FIGURE 8. INTEGRATING INFRASTRUCTURE [9]
The Integrating Infrastructure provides a set of generic IT service entities for model
engineering and model-driven enterprise operational control and monitoring, especially in
heterogeneous environments [2]. The components of the Integrating Infrastructure are as
shown in figure 8.
Control on execution of the Implementation Description Model is provided by the
Business Entity, which receives the Events and creates occurrences of the related Domain
Process and all its contents. Process Control, Resource Management, and Activity
Control, all part of the Business Entity, analyze the model contents, assign the resources,
identify the required information, and connect to the necessary Information Technology
Resources and the Manufacturing Resources, through the Common, Information, and
Presentation Entities [2], [9].
The Business Entity controls communication through networks (Common Entity),
provides access to databases (Information Entity), and communicates with people,
machines, and applications (Presentation Entity). The Management Entity provides the
necessary system services to configure and manage the Integrating Infrastructure itself
[9].
Page 10
9.0 CIMOSA MODELING AND THE SYSTEM LIFE CYCLE
CIMOSA explicitly distinguishes between Enterprise Engineering and Enterprise
Operation, placing emphasis on the need for Enterprise Engineering as a discipline
similar to Product Engineering. Therefore the life cycle phases for Enterprise Engineering
should include both model and implementation validation, followed by an explicit release
for operation [2].
FIGURE 9. CIMOSA MODELING AND ENTERPRISE SYSTEM LIFE CYCLE [2]
The relation between the process of Enterprise Modeling and the different phases of the
enterprise system life cycle are shown in figure 9. Starting from the relevant Enterprise
Objectives and Constraints, and using the appropriate part of the CIMOSA Reference
Architecture, the System Requirements for the part of the operation to be modeled are
defined. This results in a Particular Requirements Definition Model, which is then the
base for the System Design Specification. System specialists will do the system design
Page 11
specification, but CIMOSA will always maintain a translation to the business users
constructs to enable him to use and maintain his model [9].
The resulting Particular Design Specification Model and the contained Specified
Functional Entities, guide the system implementation phase (System Build and Release).
The system design is realized either through reuse of existing resources, or by buying or
building new ones. Installation and verification of their operation according to the design
specification is a major part of the system implementation phase [2]. Any deviation from
the design specification is recorded in the Particular Implementation Description Model.
After verification, the formal model is released, prior to system transfer into operation. A
formal model release is also defined for any model maintenance reflecting changes of
business processes in the course of adaptation of the enterprise operation [9].
CIMOSA ENTERPRISE SYSTEM LIFE CYCLE
FIGURE 10. CIMOSA CONCEPT AND APPLICATION [9]
The use of CIMOSA in model engineering as well as in operational control and
monitoring is summarized in figure 10. Using the CIMOSA Reference Architecture,
Particular Enterprise Models are engineered under the control of the Enterprise
Page 12
Engineering Implementation Model. The latter will usually be implemented in a CAE
Tool, which guides the user through the engineering phases of the CIMOSA System Life
Cycle [9]. The released Particular Implementation Model is then used to directly drive the
operation through monitor and control of the relevant product life cycle phase, and their
business process implementation. The Integrating Infrastructure links to the enterprise
resources. This link is required for both model creation as well as for maintenance of the
model as up-dates or extensions [9].
10.0 CIMOSA DOMAINS
Enterprise Operation Environment
Non-CIMOSA Domain
Non-CIMOSA Domain
DM2
DM3
Enterprise Management
Business Objec.
& Cons
Released Enterprise Model
Enterprise Operation
Feedback
Knowledge
on
Business
Processes Change Request
CIMOSA
Domain
DM1
Enterprise Modeling Process
Enterprise Engineering Environment
Process
FIGURE 11. CIMOSA AND NON-CIMOSA DOMAINS [3]
In this section the CIMOSA Business Modeling Process is represented as a set of Domain
Processes (DP) and Enterprise Activities (EA). The use of the CIMOSA Business
Modeling Process in the Enterprise Engineering Environment and its relation to the
Enterprise Operation Environment is illustrated in figure 11. Defining the Enterprise
Enterprise Engineering
Environment
Modeling
Environment
as a CIMOSA Domain enables identification of Domain
Relationships to the non-CIMOSA Domains in the operational environment. Major
information exchanges are indicated as domain inputs and domain outputs.
Page 13
Complete DM = Domain
DP = Domain Process
E = Events
DM1-Enterprise Modeling
E1
E3x
E32,3
E4
E33
E5
DP1
Requirements Definition
DP2
Design Specification
DP1
Implementation D’ption
List of Events
E1 = Modeling Request
E4
E31
E5
DP1
Model Maintenance
Request
(Domain
E3x = Change
Internal)
Request
(Domain
E4
=
Complete
E32
E6
E7
E2
E2 = Change
External)
E8
E33
Requirements
Definition
E5 = Design Specification
E6 = Implementation
Complete
Description
E7 = Model Released
E8 = Feedback on Change Request
(Domain External)
FIGURE 12. DOMAIN PROCESSES [3]
A set of Domain processes under the Enterprise Modeling Domain (DM1) is shown in
figure 12. The internal and external Events indicate the start condition for different
Domain Processes and the completion of the resulting models. Change requests arising
from the operations during the use of the model lead to model maintenance and
modification [3].
In the following sections, the Requirements Definition Modeling Process has been
detailed to two levels of decomposition. The decomposition of the other Domain
Processes and a detailed description of the CIMOSA Modeling Process will be made
available in Ref. [3].
Page 14
REQUIREMENTS DEFINITION MODELING
DP1 Requirements Definition
BP 1.4
Info. Anal
BP 1.7
BP 1.1
BP 1.2
BP 1.3
Domain
Behavior
Operational
Analysis
Analysis
Establishment
BP 1.5
Resr. Anal.
Consistency
Checking
E4
BP 1.6
Org. Anal.
E3x
E1
FIGURE 13. FIRST LEVEL OF DECOMPOSITION – REQUIREMENTS DEFINITION [3]
E3x
The first modeling phase of the CIMOSA Business Modeling Process is concerned with
defining the requirements for the part of the enterprise to be modeled. The system
requirements are expressed in terms of CIMOSA constructs available from the CIMOSA
Reference Architecture [3].
The definition of business requirements results in a CIMOSA Requirements
Definition Model. This model expresses all the business needs related to function,
information, resources, and organization, which are to be implemented in the CIM system
of the part of the enterprise under consideration [3]. The first level of decomposition of
Domain Process DP1, ‘Requirements Definition Modeling’, is shown in figure 13. The
modeling process may either be started by a management request (Event E1), or by a
change request (Event E3x) issued by any other modeling domain process. Event E4
indicates the completion of DP1 and the availability of the Requirements Definition
Model.
Business Process, BP 1.1, defines and establishes the business area to be modeled,
(Domain Establishment). The functional contents and its process behavior (dynamics) is
analyzed and documented in BP 1.2 and BP 1.3. The results are further analyzed and
structured into models of information, resources, and organization in BP1.4, BP 1.5, and
BP1.6 respectively. The final task is concerned with the consistency of the Requirements
Definition Model, which is controlled by BP1.7. Since the model represents the business
functionality and behavior, the supporting modeling tool may provide process animation,
supporting consistency checking of the model dynamics [3].
Page 15
DOMAIN ESTABLISHMENT
BP 1.1 Domain Establishment
EA6
Elaborate
EA 1-4
E1
Identify Domain, its
E3x
Obj/Constr,
EA5
Declarative Rules
Define
EA7
Domain Processes
Complete
Relationships, Events
Template
FIGURE 14. SECOND LEVEL OF DECOMPOSITION – DOMAIN ESTABLISHMENT [3]
The second level of decomposition of Business Process BP 1.1 is shown in figure 14. The
boundaries of a Domain to be modeled are defined by identifying its inputs and outputs.
Domain inputs and outputs may be triggering events and/or physical or information
objects, all having a distinct origin and destination [3]. Domain objectives and constraints
are derived from those defined for the total organization. All parts of the domain
description are recorded in the Domain Template.
11.0 SUMMARY AND CONCLUSION
Enterprise Integration has not yet become the common industrial goal, nor the specific
day-to-day operational tool in the manufacturing industry. Lean enterprises, business reengineering, concurrent engineering, management of change, etc., that are identified as
current management concerns, should be viewed as subsets of enterprise integration.
This paper has focused on the CIMOSA Business Modeling Process, with emphasis on
the close relationship with the phases of the CIMOSA System Life Cycle.
With the CIMOSA Business Modeling Process, a particular Requirements Definition
Model and a Design Specification Model can be elaborated in a structured way by
applying analysis rules and CIMOSA modeling constructs. The development of a
particular enterprise model takes place in clearly defined relationships between the
modeling process and the System Life Cycle. Standardization efforts on enterprise
integration are currently in progress on the ISO level and in various international
organizations supporting European and international standardization.
Page 16
BIBLIOGRAPHY
1. Nanua Singh, Systems approach To Computer – Integrated Design And
Manufacturing, John Wiley And Sons Inc, New York, 1996.
2. K. Kosanke, "CIMOSA – Overview and Status", Computers in Industry, Volume 27
(2), pages 101-109, 1995.
3. K. Kosanke, F. Vernadat, M. Zelm, "CIMOSA: Enterprise Engineering and
Integration ", Computers in Industry, Volume 40 (2, 3), pages 83-97, 1999.
4. G. Berio, F. Vernadat, "New Developments in Enterprise Modeling Using
CIMOSA", Computers in Industry, Volume 40 (2, 3), pages 99-114, 1999.
5. M. Zelm, F. Vernadat, K. Kosanke, "The CIMOSA Business Modeling Process",
Computers in Industry, Volume 27 (2), pages 123-142, 1995.
6. T.J. Williams, P. Bernus, J. Brosvic, D. Chen, L. Nemes, "Architectures for
Integrating Manufacturing Activities and Enterprises", Computers in Industry,
Volume 24 (2, 3), pages 111-139, 1994.
7. "Introduction To CIMOSA", www.rgcp.com/cimosa.htm, 11-11-99.
8. "Enterprise Modelling", www.rgcp.com/modelling.htm, 11-11-99.
9. "CIMOSA: A Primer Of key concepts, purpose and business value",
http://cimosa.cnt.pl/Docs/Primer/primer93.html, 11-11-99.
Page 17