Requirements for Simulation Tools in Enterprise ...

Enterprise Modelling and Integration: Current Status and Research Perspectives F.B. Vernadat MACSI/INRIA & LGIPM, University of Metz, France

CAD, CAE, CAD/CAM, Factories of the Future, CE, CIM, ...

CIM is dead ! Long live EI ... F. Vernadat, Université Metz, France

Current Business Trends

QCD

Globalisation of economies  Focus on customer satisfaction  Time-based & price-based competition  Lean management / Autonomous units  Total quality management  Agility  Networked (extended/virtual) enterprises 

F. Vernadat, Université Metz, France

New trends Fact: world-wide availability of - information/knowledge - technology - capitals ==> Increased Reactivity ==> Better Management of Change ==> Creativity and Innovation ==> Focus on People & Knowledge Mgt F. Vernadat, Université Metz, France

New Needs Systems interoperability  Process management & co-ordination  Teamwork & CSCW of autonomous units in networked organisations  Model-based engineering & operations 

==> Enterprise Modelling and Integration (EMI) Technology F. Vernadat, Université Metz, France

Enterprise Modelling and Integration: Myth or Reality? Enterprise Engineering and Integration  Definitions  Frameworks  Architectures  Standardisation  EMI Trends and R&D Needs  Conclusion F. Vernadat, Université Metz, France

EMI Definitions Enterprise Engineering & Integration - to engineer = to design, plan, evaluate and test, or revise current operations - to integrate = to remove boundaries

Enterprise Integration (EI): deals with increasing interoperability among people, machines and applications to enhance synergy within an enterprise (or a network of enterprises) to better achieve business objectives (or mission) Has technological and organisational dimensions

Keys to EI = business process communication, co-operation and co-ordination

F. Vernadat, Université Metz, France

EMI Definitions (cont'd) EI = to provide the right information at * the right place and * the right time!

F. Vernadat, Université Metz, France

EMI Definitions (cont'd) and to enable communication between * people, * machines and * computers observe understand Customer influence simplify and with Orders * customers and Products supplier * suppliers monitor & control Material Orders

F. Vernadat, Université Metz, France

EMI: The Needs Business world

IT world

Process model

Manufact. Appli. Organization model

Legacy Appli. (Business Processes) F. Vernadat, Université Metz, France

Business language

Network

Product model

Computer

Prod. Conf. Mgt. Appli.

INTEGRATION PLATFORM

Des. & Eng. Appli.

External networks Middleware

Basic IT services

AIT View of EI

Supply-chain representation

supplier factory F. Vernadat, Université Metz, France

stock area customer

EMI: The Problem Modeling Framework

Organisation/ Economic aspects

Human aspects

Enterprise Model (Semantic Unification)

concepts

concepts Physical Flow

System A

System B (Information Flow) Information Flow

Technical aspects F. Vernadat, Université Metz, France

Integrating Infrastructure (IIS)

Co-ordination aspects

EMI: Integration Levels CIM/EI Integration levels BUSINESS INTEGRATION ENV 40 003

Coordination

CIMOSA

GERAM

CALS

Organisation and human aspects

APPLICATION INTEGRATION

Co-operation

BP/workflow execution engines/CSCW EDI/EDIFACT STEP/PDES HTML SQL/OQL/ODMG KQML/KIF PIF WPDL Integration services OPAL AIT-IP

PHYSICAL SYSTEM INTEGRATION OSF/DCEOMG/CORBA Internet/WWW

Communication ISO-OSI F. Vernadat, Université Metz, France

TCP/IP

ASI

ATM

Fast Ethernet

CIM/EI Evolution

Enterprise Engineering (EE) 

EE deals with the design/redesign and optimisation of the operations and organisation of business entities  EE either concerns the reengineering of: – operative part (physical architecture) – information and control part (logical archi.) – human part

of business entities (e.g. business processes, application systems, plants, enterprise, network of enterprises) F. Vernadat, Université Metz, France

Enterprise Life Cycle Life-cycle stages activity types

Identification

Conceptualisation Requirements

Preliminary design Design

Detailed design

Implementation Operation Decomissioning

GERA Life-Cycle Concept F. Vernadat, Université Metz, France

Enterprise Life History Life-cycle stages activity types

Identification Enterprise Concept

Engineering Projects

Requirement Redesign continuous improvement project

Design Implementation

Operation Decommission

Enterprise Operation

Decomissioning project Time (Life History)

F. Vernadat, Université Metz, France

Enterprise Modelling (EM) 

EE relies on Enterprise Modelling (EM)



EM is the art of externalising enterprise knowledge which can be reused or adds value to the enterprise



EM describes various aspects of enterprise structure, behaviour and organisation

F. Vernadat, Université Metz, France

Modelling Views

Functional Model

Organisation Model

ABC Enterprise

Information Model

Resource Model

Economic Model F. Vernadat, Université Metz, France

Added Value of EM The four essential goals of Modelling, i.e.: to understand to learn (what-if scenarios) to experiment (analyse, compare, test, evaluate performances, decide) to operate govern developments in Enterprise Modelling Major advantage: to build a common consensus on how enterprise operations work (or should work) F. Vernadat, Université Metz, France

What needs to be modelled? - Products and material flows - Business Processes - Technical resources - Data/Information/Knowledge - Organisation/Decision levels & centers - Human roles and aspects - Costs -…

F. Vernadat, Université Metz, France

Enterprise Modelling Process Design/Reengineering Phase

AS-IS model

Conceptual Model of existing system

Transformation

Conceptual Model

of future system Conceptual Level

Existing System

Real-world Analysis Phase

Reengineered System Implementation Phase

Rule: Must rely on a participative approach F. Vernadat, Université Metz, France

TO-BE model

PERA (Purdue Enterprise Ref. Architecture) An Enterprise Consists of 3 Major Concepts Enterprise Definition

Enterprise Physical Syst. & Facilities

People

Enterprise Logical Systems

Enterprise Dissolution F. Vernadat, Université Metz, France

PERA (Purdue Enterprise Ref. Architecture) The PERA Model Combines these 3 Concepts in a Systematic "Phased" Approach 1

Feasibility Study

2 3

Policies Req'ments Functions Flow Diags

5 7 9

4 6

Enterprise Definition

8 10

Conceptual Engineering

12

11

13

Prelim. Engineering

14

15

16

Detailed Engineering

17

18

19

Construction

20

21

22

23

24

25

Human Roles

Enterprise Logical Systems

Facility & F. Vernadat, UniversitéEnterprise Metz, France Phys. Syst.

Operations & Maintenance

Decomissioning Enterprise Dissolution

Fundamental types of flows   

Material flows (e.g. products, parts, …) Information/decision flows (e.g. data, doc.) Control flows (or workflow)

F. Vernadat, Université Metz, France

Flow Superposition

Event Activity

Object Business Process 1 EV2

EV1

Resource

FINISH START

Business Process 2 EV2

FINISH START

F. Vernadat, Université Metz, France

Workflow systems

F. Vernadat, Université Metz, France

Business Process Example (CimTool by CimOsa/RG) Start

CdCTechniqueOrgane CdCDone

DécompositionEnPièces

LancerEtude

EtudePièce ResteAfaire EtudesPiecesFaites

Montage/AssemblageOrgane MontageOk

ValidationOrgane ValidationOk

DossierTechniqueOrgane DossierTerminé

Finish

F. Vernadat, Université Metz, France

@PièceSuivante

Enterprise Activity Example ENTERPRISE ACTIVITY Name: TechnicalFileRealisation INPUTS: Function Input: PartDrawing TestReport Control Input: Resource Input: ProjectLeader OUTPUTS: Function Output: TechnicalFile Part-OCM Control Output: Resource Output: Required Capabilities: Ending Statuses: Complete, Incomplete, Canceled F. Vernadat, Université Metz, France

Essential Control Flows (structured processes) Sequence:

Conditional Branching:

Parallelisation: (sync. or async.)

Rendez-vous:

Loop: F. Vernadat, Université Metz, France

Additional Control Flows (ill--structured processes) AND AND-case:

A

B

C

D OR

OR-case:

A

B

C

D XOR

XOR-case:

F. Vernadat, Université Metz, France

A

B

C

D

Process vs. Resource Behaviour Chains of Activities

Processes

Capabilities/ Competencies

Fonctional operations Operations & States

Machines F. Vernadat, Université Metz, France

What has to be done

Resources (agents)

Applications

The doers

Humans

Process vs. Resource models CustomerCreation OEC

OrderProcessing FINISH

NCO event p1 p2 START

Process Model

OPS

OrderEntry OrderProcessing

OEC: OrderEntryClerk OPS: OrderProcessingSystem

p1 + p2 = 1 In

Start (CC) and not (Start (OE)) Create Customer (CC)

Out

Look for work to do

End (CC) Start (OE) Order Entry (OE)

Start (DR)

Receive Order

Resource Model

End (DR) Out of work

Daily reporting (DR)

End (CCu)

Check Customer (CCu)

Check Order F. Vernadat, Université Metz, France

CIMOSA Modelling Approach Developed by EP Consortium AMICE (86-94) Based on an event-driven process-based modelling approach CIMOSA views any business entity as:  

a large collection of concurrent business processes triggered by events a large collection of interacting functional entities (human or technical agents)

F. Vernadat, Université Metz, France

CIMOSA Principles Instantiation of Building Blocks Generation of Views

Organisation View Resource View

Information View Function View

What

How

Requirements Definition Model

Reference Architecture Generic Constructs

Partial Models

Design Specification Model

Particular Model Implementation Description Model

Do CIMOSA Cube F. Vernadat, Université Metz, France

Derivation of Models

CIMOSA Modelling Constructs Triggers Process

Event

Made of Responsible for

Has Activity

Object View input/output

Responsible for

Requires Capability/ Competency Set F. Vernadat, Université Metz, France

Organisation Unit

Provides

Resource

CIMOSA Modelling Vision DM1

DM3

DP3.1 DP3.2

DP1.1

Events & Results DM2

Legend: DM = Domain DP = Domain Process BP = Business Process EA = Enterprise Activity BRS= Behavioural Rule Set

DP2.1 DP2.2 DP2.3 DP 2..1

Control I/O

EA1

BP2.1.1

Event1

BP2.1.2

DP2.1 EA1

BRS EA4

EA3

EA4

F. Vernadat, Université Metz, France

EA5

Function Input

EA4

EA5

Event2 EA2

Result a

EA2

EA3

Result b

Resource I/O

Function Output

The CIMOSA enterprise model

Order

Order

Reality Product

Material

Enterprise

Method Tool

CIMOSA Enterprise Model DP 2.1

DP2.1 Event1

DM2 DP2.1 DP2.2

DP2.3

BP2.1.1 EA2

F. Vernadat, Université Metz, France

EA1 EA3

BP2.1.2 EA4

EA5

Event2

EA1

BRS EA4

Result a

EA5 EA2

EA3 Result b

CIMOSA Model

Example Customer

Order

BP1 Administration Invoice Events & Results

BP3 Quality Assurance

Customer Product

BP2 Manufacturing

Shop Floor Order a

Shop Floor Order b

EA1 machining

EA3 store Purch. Parts

EA2 painting

Product a

EA4 assembly

BRS

Shop Floor Order b Supplier

BP = Business Process EA = Enterprise Activity BRS = Behavioural Rule Set F. Vernadat, Université Metz, France

Product b

Order Status

Parts Purchased Parts

EA4 assembly

Assembly Resources

Product b

Resource Status

Networked enterprises Organisation Center B

Organisation Center A

Data Center

Organisat. Unit (ctrl flow)

Human agents

F. Vernadat, Université Metz, France

Information and control flow

Physical agents

Physical flow

Organisat. Unit (ctrl flow)

Physical agents

Data Center

Human agents

The extended enterprise and its relations Supplier Order

Order Customer

Material

Reality

Enterprise

Product

Method Tool

CIMOSA Extended Enterprise Model DM3 Supplier Order

DM1 Customer =

DP1.1

Product

DM2 Enterprise Order

F. Vernadat, Université Metz, France

Material

DP2.1 DP2.2

DP2.3

DP3.1

DP3.2

CIMOSA Model

The virtual enterprise and its relations Supplier

Order

Order Customer

Reality

Material Product

CIMOSA

Virtual Enterprise

Method Tool

Virtual Enterprise Model DM1 Order

=

DP1.1

Order

Events & Results

DM3 DP3.1

DM2

Product

F. Vernadat, Université Metz, France

DP2.1 DP2.2 DP2.3

DP3.2

CIMOSA Model Material

CEN ENV 12 204 Enterprise Modelling Constructs between

ENTERPRISE OBJECT

state of view of

RELATION

OBJECT STATE

can play the role of

type of BUSINESS PROCESS

OBJECT VIEW involved in ORDER

RESOURCE

used in

SEQUENCING RELATIONSHIP

employs

combined by

PRODUCT

ORGANISATION UNIT

provides CAPABILITY SET

F. Vernadat, Université Metz, France

ENTERPRISE ACTIVITY

required by

used in

EVENT

GERA: Generalised Enterprise Reference Architecture Generic Partial

Views {

{

{

} Particular

Subdivision according to genericity

Instantiation Identification

Customer service

Concept

Management and control

Requirements

}

Subdivision according to purpose of activity

}

Subdivision according to physical manifestation

}

Subdivision according to model content

}

Subdivision according to means of implementation

Software Hardware

Preliminary design Design

Resource Organisation Information Function

Detailed design Implementation

Operation Decommission

Life-cycle phases F. Vernadat, Université Metz, France

Machine Human Reference Architecture

Particular Architecture

EMI: Standardisation Effort ISO TC 184/SC5/WG1: ISO IS 14258 Rules and Guidelines for Enterprise Models ISO DIS15704 Requirements for Enterprise Reference Architectures

CEN TC 310/WG1 ENV 40 003 Framework for Enterprise Modelling ENV 12 204 Constructs for Enterprise Modelling ENV xxx: Integrating Infrastructure to support Model Enactment

IFAC IFIP Task Force GERAM (Generalised Enterprise Reference Architecture and Methods) (Appendix to ISO DIS 15704) F. Vernadat, Université Metz, France

EMI Standardisation Road-map (CEN + ISO) IS 14258 Rules and Guidelines for Modelling

FWI: Rules and Guidelines for Infrastructures

Related Standards

ISO WD 15704: Requirements for Enterprise Reference Architectures and Methodologies State of the Art: GERA, ENV 40003 Modelling Framework)

FWI: Process

Repr.

ENV 12204 Constructs for Mod. FWI: Icons for Mod. Constructs FWI: IT rep. for Mod. Constructs

F. Vernadat, Université Metz, France

FWI: Human related Representations

FWI: Infrastructure Framework - State of the Art: EMEIS

FWI: Human Roles

FWI: Model Developm. Services

ISO 14000

FWI: Human Skills

FWI: Model Execution Services

ODP

FWI: (Human Behaviour?)

FWI: General IT Services

ISO 9000

others (tbd)

EMI: Results achieved so far Early CIM Programmes: - IPAD, ICAM, CAM-I, GRAI - PDES, STEP/EXPRESS  IiM and EI Programmes: - CALS (EDI + STEP + HTML) - AMICE, CNMA, EIP, NIIIP, NGM, AIT  IMS Programme  ICEIMT EU-US Initiative (92, 97) 

F. Vernadat, Université Metz, France

Enterprise Modelling Results IDEF suite of methods (IDEF3)  CIMOSA, PERA & GIM  Others: ARIS (Scheer), IEM (IPK), ...  TOVE Ontologies (Toronto)  Yu's organisational model (Toronto)  Factory Data Model (LUT)  ... ==> Workflow Mgt Systems & EM Tools 

(ARIS ToolSet, IBM Flow Mark, FirstSTEP, PrimeObject, NCR Metis...) F. Vernadat, Université Metz, France

EM: What's the Problem? of languages DIVERSITY

Tower of methods of Babel of tools situation

Poor semantics of EM construct def. ==> UEML standard (Unified Enterprise Modelling Language) F. Vernadat, Université Metz, France

Enterprise Integration Results CIMOSA IIS (ESPRIT AMICE)  CIM-BIOSYS (LUT)  AMBAS (FAW)  CCE-CNMA (ESPRIT)  PACT and SHADE (Stanford)  AIT-IP, AIT-OPAL (ESPRIT)  EIF, NIIIP (US) ==> OSF/DCE & OMG/CORBA 

F. Vernadat, Université Metz, France

CIMOSA-IIS Machine Dialogue

Business Process Control

Human Dialogue Application Dialogue

Naming

COMMON SERVICES request

response

F. Vernadat, Université Metz, France

System Wide Data

Resource Management

PRESENTATION SERVICES

Communic ation

BUSINESS

Ac tivity Control

Data Management INFORMATION SERVICES

SERVICES

Registration

Security

Time

OMG CORBA Framework OMA

Application Objects

Common Facilities

Object Request Broker

Object Services Object Implementation side

Client side

Legacy system C++

Ada C C++ client

F. Vernadat, Université Metz, France

IDL

CORBA

IDL

C Object Implementation

AIT-IP (EP 22148) Actor Directory

Information Model

BSA

GES

Systemwide Actor Directory Mgt Services

AFE

Systemwide Information Mgt Services

Integration Platform Software Bus (CORBA)

MFE

HFE

DFE

Exchange Protocol (e.g. MMS)

Virtual Terminal Management

Database Engines (SQL, OO, ...)

F. Vernadat, Université Metz, France

CFE Network Management (e.g. TCP/IP)

AIT OPAL (EP 20377) Execution Environment

WWW-Browser MRP CAD PDM Native API

User defined (high level) applications

Encapsul. modules

Business process / virtual folder desktop

Hypermedia facilities Bus. process Virt. folder interpretor system serv.

Central services

Middleware (request broker)

Development Environment

Repository (Meta Model) services

F. Vernadat, Université Metz, France

WPDL Tools to define business processes

STEP-EXPRESS Tools to define data models and instance editor

EI: What's the Problem? No off-the-shelf Plug & Play solution  Lack of stable standards (mostly de facto standards)  Poor support for process coordination in large distributed envts 

Encapsulation of legacy systems can hardly been made systematic F. Vernadat, Université Metz, France

Research Agenda Item 1: Meta-models and meta-meta models UEML (Unified Enterprise Modelling Language) ==> standard interface for any EM tool must be strongly business user-oriented requires semantic definition of constructs EM ontologies ==> formal definition of fundamental EM concepts (still to be developed) Common vision of EMI in industry ICEIMT 97 & IEMC 99 F. Vernadat, Université Metz, France

Research Agenda Item 2: Component-based enterprise engineering (CBEE) towards the digital model of the enterprise the way for the future of EE - "components" or "patterns" are not software modules - they are knowledge chunks ==> knowledge management Serious issues: for business users: model maintenance (wrt ent. evolution) for tool builders: model configuration management for component vendors: to provide component models CEN TC 310 / IFAC-IFIP TF F. Vernadat, Université Metz, France

Research Agenda Item 3: EM-based Modelling and Simulation Tools Goals: to support distributed communicating processes to analyse co-odination mechanisms (supply-chains, extended/virtual enterprises) based on UEML Needs: reconfigurable architectures agent-based distributed simulation techniques F. Vernadat, Université Metz, France

Research Agenda Item 4: Organisational and socio-cultural aspects organisational structures (virtual enterprise, extended enterprise, network enterprise) communication practices among agents may have influence on process execution human roles and competencies "soft issues" (human behaviour, beliefs, commitment, obligation, trust, ...) ICEIMT 97 & IFAC 99 F. Vernadat, Université Metz, France

Research Agenda Item 5: Model interoperability ==> How to formalise model properties such as: completeness? consistency? coherency? ambiguity? quality? fitness to objectives? These are fuzzy properties because: enterprise engineering is not a «closed-world» common-sense, if considered, is hard to formalise freedom is left to define exceptions non determinism is allowed world is made out of fragments; distributed real-world F. Vernadat, Université Metz, France IEMC 99

Conclusion 

EM and EI: a reality in many companies, but so far not fully satisfactory



EM take-over by industry has been longer than expected



EI not receiving enough R&D attention



EM & EI largely ignored by SME's

F. Vernadat, Université Metz, France

Any questions?

F. Vernadat, Université Metz, France