Transcript Enterprise Modeling for System Integration

Model-based Enterprise
Integration
MAI Lab.
2000 5/17 이기창
Overview

Critical problems in industrial automation by ICAM
Program in 1983




Information could not be controlled by users
Changes were too costly and time consuming
Systems were not integrated
Data quality was not suitable for integration
2/34
Overview

Benefits of the integration of the technologies






Interactive system which enables manufacturing
functions to communicate with each other
Accurate data transferability
Faster responses to data changes
Increased flexibility towards introduction of new products
Improved quality of the products
Reduction in lead times
3/34
Overview

Research Trends in CIM





Justification of CIM and management strategies for CIM
Enterprise integration for CIM beyond and within
geographical boundaries
Advanced tools and technologies for the application of
CIM
Manufacturing system modeling
Application of artificial intelligence for integrated
intelligent manufacturing system
4/34
CIMOSA: enterprise engineering
and integration
K. Kosanke, F.Vernadat, M.Zelm
Dept. of Manufacturing Engineering, Loughborough
University, UK.
Performa Consultants Ltd.
COMPUTERS IN INDUSTRY, 1999, V.40, 83-97
Introduction

Goal of integration


To improve the overall system efficiency by linking its elements
by means of communication networks and thereby obtaining a
higher responsiveness and effectiveness of the whole system…
Situations

Environments



Long term predictability – exceptional case
Partnerships – extended and virtual enterprises
Enterprise systems





Complex entities with a large number of elements
Organized in intricate networks of departments, divisions, plants,
etc.
Distributed geographically
Cooperate or deal with many customers and suppliers
Dynamic and continuously changing elements and relationships
6/34
Evolution of the meaning of system
integration
7/34
Scope of Enterprise Engineering

General definitions


Enterprise engineering - define, structure, design and
implement enterprise operations as communication
networks of business processes, which comprise all their
related business knowledge, operational information,
resources and organization relations
Enterprise integration – provide the right information at
the right place at the right time and thereby enable
communication between people, machines and
computers and their efficient cooperation and
coordination
8/34
Identification and Use of
Information

Process models




A very efficient means both for identification of the
information and for its location
Computer supported model will make possible the
evaluation of the process alternatives
Decision support on any level the the organization for
strategic, tactical or operational planning
Common understanding in the enterprise
9/34
Enterprise Modeling

Both methods and tools for modeling and model use have
to be computer supported
10/34
CIMOSA Modeling


Functionality – enterprise activity (EA)
Behavior – behavioral rule set (BRS)
11/34
GERAM



GERAM is the work of the IFAC/IFIP Task Force on
enterprise reference architecture
GERAM defines a toolbox of concepts for
designing and maintaining enterprises for their
entire life-cycle
GERAM is a new framework which encapsulates
and orders the previous architectures(CIMOSA,
PERA, GIM) providing an overall structure to use
those methods and modeling techniques
12/34
GERAM

7 major components

Generic Enterprise Reference Architecture (GERA)


Generic Enterprise Engineering Methodology (GEEM)


Partial models common to all enterprises
Generic Enterprise Module (GM)


Set of languages and tools used for enterprise engineering
Generic Enterprise Model (GEM)


Documents about processes of enterprise integration
Generic Enterprise Modeling Language (GEML) & Generic
Enterprise Modeling Tool (GEMT)


Enterprise lifecycle modeling framework
Products, standard implementation of components
Generic Enterprise Theory (GT)

Ontologies or meta-models
13/34
GERAM EE&I Framework
14/34
GERA Modeling Framework
15/34
GERA Modeling Framework
16/34
Conclusion
Through application of EE&I to industry, qualitative
and quantitative benefits have been obtained
 The emphasis on enterprise modeling applications
is still enterprise re-engineering.
 Modeling are usually not kept up-to-date and not
used for operational decision support
 Tools with a user interface are becoming more
available and general use of enterprise modeling
becomes feasible

17/34
A modeling language for the
design and execution of enterprise
models in manufacturing
Jose P.O. Santos, J.J.Pinto Ferreira, Jose M. Mendonca
Dept. of Mechanics, University of Aveiro, Portugal
INT. J. COMPUTER INTEGRATED MANUFACTURING,
2000, V.14, N.1, 1-10
Introduction

Objective of this paper

To propose an enterprise modeling language(EML) that
enables the development of executable models
19/34
Positioning in the Scope of GERAM
GERA
concepts
PEMs
Reusable
Reference models
EMOs
(shop floor
Operator skill)
EEM
Methodologies
(CIMOSA…)
Proposed EML
GEM
meaning
EMTs
EMD
Enterprise operating system
20/34
EMEIS Architecture

Enterprise Model Execution and Integration Service(EMEIS,
ENV 13550)

Concerned with the services required to develop, execute and
integrate enterprise models on an open platform
Model development services
Interaction
EMEIS
Model
Model execution services
IT base services
21/34
Model Requirements

The model aims at covering part of the enterprise
shop floor control engineering meeting additional
requirements






Cover the definition of a finite set of elementary activities
Computer executable
Support real-time operations and asynchronous events
Support activity description and enactment
Provide enough formalism to support multitask
Support the distribution of the model itself across the
network
22/34
Proposed Enterprise Modeling
Language

Model building block (MBB)



To organize the enterprise behavior in reusable blocks
MBBs and Partial enterprise models (PEMs) previously
developed can be reused
MBB encompasses an Action model table (AMT)



AMT : an ASCII table containing a part of enterprise
behavior using the EML primitives
MBB is defined as an object-oriented library class
Model execution

The kernel uses services provided by other MBB objects
or the functional operation integration platform (FOIP)
library
23/34
Proposed Enterprise Modeling
Language
MBB1 : Gearbox machining
PEM
MBB1.1
Action’s model table
i
1
2
3
4
4
5
Prei
S2=2
MBB1.2
MBB1.3
……………..
Actioni
BEGIN
R1.MovPart(MS1, WC1)
M1.StartPgm(part.iso)
R1.MovPart(WC1, FP1)
END
BEGIN
Sti
Posti
0
0
S2:=1
Depi
S2:=2
……………..
24/34
Proposed Enterprise Modeling
Language

Columns of the action model table





Action precondition (Prei) : boolean expression, enabling
the beginning of the action execution
Action (Actioni) : describe the actions that must be
executed (object method)
Action state (Sti) : 4 execution states – not initiated
(IDLE), processing (PROCESSING), error terminated
(ERROR), successfully terminated (OK)
Post action (Posti) : executed when the action is
successfully finished
Dependence action (Depi) : synchronize the action
execution
25/34
Execution Kernel

Roles of execution kernel



Reads each MBB’s AMT and calls the correspondent execution
object from functional operation integration platform (FOIP)
Calls the specified object method and changes the respective
action state to ‘PROCESSING’ state
5 conditions for each action to be initiated





Precondition field must be true
Previous action should be finished successfully
Action state field must be ‘IDLE’
Action must be not dependent on others
The object that provides the action mush not be locked by
another MBB
26/34
Functional operation integration
platform (FOIP)


Inspired by reference model EMEIS but not EMEIS
compliant
Features



Computer object-oriented library (written in SmallTalk)
Provide model execution service (MXS)
Provide information technology base service
27/34
Functional operation integration
platform (FOIP)
FOIP class
Model development services
MFG class
Model
Execution
KERNEL
Model execution services
IT base services
Instantiated
To execute
Mfg. Functional entities
28/34
CIMOSA Models based on the EML

CIMOSA –
driveshaft
machining
29/34
CIMOSA Models based on the EML

CIMOSA
production
model based
on MBB
30/34
Conclusion



Proposed enterprise modeling have been
successfully used in various scenarios to control a
FMS
MBB-based language fulfills most of the CIMOSA
procedural rules
Proposed solution enables software integration


Computer interpretable model
Extension of EML, information technology
infrastructure is future work
31/34
Review

International efforts about enterprise modeling

To standardize enterprise modeling and integration




CEN/TC310/WG1
ISO TC 184/SC5/WG1
International conference on enterprise integration and
modeling technology (ICEIMT)
To improve enterprise reference architecture


AMICE Consortium
IFIP/IFAC Task Force
32/34
Review

Major components to enterprise integration

Data sharing



Communication


Standard for data exchange (e.g. STEP)
Redundancy, inconsistency between functional modules
(e.g. BOM inconsistency between engineering, sale,
manufacturing)
Integration infrastructure (e.g. CORBA, DCE)
Operation coordination


Resource allocation for global objective
Model-based or theory-based decision support (e.g.
executable model consisting AMTs)
33/34
References
CEN TC310 WG1 : Enterprise Modeling for CIM,
http://www.itfocus.demon.co.uk/tc310wg1/wghome1.html
 P. Bernus, L. Nemes, A framework to define a generic enterprise
reference architecture and methodology,
http://www.cit.gu.edu.au/~bernus/taskforce/geram/report.v1/repor
t/report.html
 F.B. Vernadat, Enterprise modeling and integration : principles and
applications, Prentice-Hall, 1996.
 S.V.Nagalinggam, G.C.I. Lin, Latest developments in CIM, Robotics
and Computer Integrated Manufacturing, V.15, 1999, 423-430.

34/34