New Applications Of GERAM to Virtual Enterprises And Networks

P.Bernus 1999

New Applications Of GERAM to Virtual Enterprises And Networks

Peter Bernus

Griffith University

June, 1999

P.Bernus 1999

Overview

• Project enterprise as a Virtual Enterprise

• Bidding and performing the project

• Virtual manufacturing / service enterprise

• Properties of VE

P.Bernus 1999

Life-cycle of a OKP (e.g. plant)

DesignPreliminary design

Detailed design

Identification

Concept

Requirements

Implementation

Operation

Decommission

GERAGERA

P.Bernus 1999

GERAGERA

Time

Redesign/refurbishproject

Plant Operation

Life history of a OKP (e.g. plant)

Plant engineeringand construction project using concurrent engineering

Decommissioningproject

Life-cycle

Resource development planning

Continuous improvementplanning

P.Bernus 1999

GERAGERA

Time

Redesign/refurbishproject

Plant Operation

Competencies

Plant engineeringand construction project using concurrent engineering

Decommissioningproject

Life-cycle

Resource development planning

Continuous improvementplanning{Company

competency

EngineeringProjectEnterprise’scompetency{Constructioncompanycompetency {Plant competency

{{

P.Bernus 1999

Relationship between life-cycles

designpreliminary design

detailed design

identification

concept

requirements

implementation

operation

decommission

operation

Project Enterprise

Plant

GERAGERA

P.Bernus 1999

The project is an enterprise

• Has ‘operations’ and ‘management’

• Is ‘virtual’ - it is not a company with assests, but it disposes over resources for the duration of the project / has mechanisms to secure the use of resources for the service/production tasks

P.Bernus 1999

Characteristic life history of project enterprise

P.Bernus 1999

Contributions to the life-cycle of a OKP (plant)

company

plant

EngineeringContractor

EngineeringSubcontractors

{{

{EngineeringProject Enterprise

ConstructionCompany

{

Infrastructureproviders

P.Bernus 1999

Operations

Management and Management and Control SystemControl System

Operations


Operations


Negotiate project

Carry out project

P.Bernus 1999

Preparedness/readiness

• The companies in a network / alliance / partnership should be ready to bid for a given type of project

• This defines management and operational competencies that must be available for successful bidding

It is the purpose of the design of the It is the purpose of the design of the management system, to co-ordinate management system, to co-ordinate objectives of the high levels with objectives of the high levels with objectives of low levelsobjectives of low levels

h=7dp=1d

h=1dp=8h

h=8hp=1h

realtime

co-o

rdin

atio

n

P.Bernus 1999

• DCs behave as an agent - the challange DCs behave as an agent - the challange is for the enterprise as a whole to also is for the enterprise as a whole to also behave as an agent (“aware enterprise”) behave as an agent (“aware enterprise”)

• The production management system of The production management system of oneone integrated enterprise will achieve this. integrated enterprise will achieve this.

Problem: how to co-ordinate non incorporated Problem: how to co-ordinate non incorporated enterprises (virtual enterprises) to achieve the same?enterprises (virtual enterprises) to achieve the same?

Traditional value chain isTraditional value chain isnot co-ordinated: the virtual not co-ordinated: the virtual enterprise is not an agententerprise is not an agent

h=7dp=1d

h=1dp=8h

h=8hp=1h

realtime

co-o

rdin

atio

n

operational interaction only, feedback fixes only individual problems

h=7dp=1d

h=1dp=8h

h=8hp=1h

realtime

co-o

rdin

atio

n

Integrated value chain is co-ordinated: Integrated value chain is co-ordinated: the virtual enterprise is an agentthe virtual enterprise is an agent

multi-level interaction: objectives are co-ordinated on every horizon (also on top!)

co-o

rdin

atio

n

co-o

rdin

atio

n

h=7dp=1d

h=1dp=8h

h=8hp=1h

realtime

h=7dp=1d

h=1dp=8h

h=8hp=1h

realtime

Consortium with limitedConsortium with limitedco-ordination: the virtual enterprise acts co-ordination: the virtual enterprise acts as an agent in a limited domainas an agent in a limited domainco-ordination onmultiple levels, e.g. joint policy adjustment (in limited domain)

co-o

rdin

atio

n

co-o

rdin

atio

n

Here the consortium has separate mgmtwith limited authority}

P.Bernus 1999

Enter into pre-agreements: for a category of products or services or for a type of project agree on common way of acting, on type of information sharing, mutuality, ways to prepare a joint bid, ...

co-o

rdin

atio

n

co-o

rdin

atio

n

H=1yp=3m

h=3mp=2w

h=2wp=5d

realtime

H=1yp=3m

h=3mp=2w

h=2wp=5d

realtime

P.Bernus 1999

Based on tender / invitation to bid set up a project to prepare a bid

co-o

rdin

atio

n

co-o

rdin

atio

n

H=1yp=3m

h=3mp=2w

h=2wp=5d

realtime

H=1yp=3m

h=3mp=2w

h=2wp=5d

realtime

P.Bernus 1999

Allocate resources to bid preparation

co-o

rdin

atio

n

H=1yp=3m

h=3mp=2w

h=2wp=5d

realtime

co-o

rdin

atio

n

H=1yp=3m

h=3mp=2w

h=2wp=5d

realtime

P.Bernus 1999

Question: do we need these strategic / tactical transactions between all partners?

Operations


Operations


Operations


Operations


Operations


The infrastructural service/product providersneed not be involved (VE has relative authonomy)

VE

P.Bernus 1999

Autonomy

• Autonomy is relative, an enterprise as an agent is autonomous in relation to a set of functions that it can perform without the need to rely on others, provided there is a presupposed ubiquitous infrastructure

P.Bernus 1999

Necessary competencies

Company

Plant

EngineeringContractor

EngineeringSubcontractors

{{

{EngineeringProject Enterprise

ConstructionCompany

{

InfrastructureProviders

P.Bernus 1999

Time

ICRDIOD

ICRDIOD

ICRDIOD

Vir

tual

ente

rpri

ses

Pro

duct

sN

etw

ork

T1 T2 T3 T4

After J.Vesterager, TUD,1999

P.Bernus 1999

Necessary competencies

EngineeringProject Enterprise


Detailed design

Identification

Concept

Requirements

Implementation

Operation

Decommission

P.Bernus 1999

Engineering Project Enterprise


Detailed design

Identification

Concept

Requirements

Implementation

Operation

Decommission

P.Bernus 1999

Plant engineering policies(ISO 9000x)

Plant engineering functionalrequirements specification(STEP)

Particular Plant engineering policies

Particular Plant Project requirements

Function (typicalengineering projectfunctions)

Information (AP)

Resource (Application type)


Quick to generatein the presenceof reference model

P.Bernus 1999

Particular Plant engineering policies

Particular Plant Project requirements

Particular project functions

STEP (AP)

Selected CAD tool type

IDEF0 semantics

EXPRESS (languagesemantics)

Resource ontology


P.Bernus 1999

Project plan(time, cost)

Product databasedesign

Selected CAD tools, contractors

Project mgmt ontology

SQL

Resource ontology (design level)


P.Bernus 1999

Types of VE

1 VE for OKP

2 Repetitive service or manufacturing

To manage the VE = supply chain management on all levels in the extended enterprise

P.Bernus 1999

Necessary ingredients for VE

• Common objectives (opportunity, economy, competitivity, interest)

• Motivation to create a VE is to create synergy of key partners by the VE to produce service/product which would have been beyond any of them if acting separately. VE based on Business opportunity

Operations Operations

Material and information flow

Supply chain

Operations

Management and Control System

The extended enterprise (may or may not be co-ordinated on tactical and strategic levels, therefore may not have the survival capabilities a single enterprise has.)

Management transactions on operational control level

Operations





Virtual enterprise is a kind of extended enterprise which acts as one autonomous entity for the purposes of its product

co-ordination transactions on all necessary levels

P.Bernus 1999

Important distinctions between types of VE based on

• Are partners of the same size (determines relevance/significance of transactions)

• Are they co-located or somehow different from the rest?

• Is knowledge shared or is it provided / owned by one member?

• Mutuality, significance, control, informedness as important distintions in forming various types of VE

P.Bernus 1999




End user

Not visible for e.u.




visible for e.u.

End user

Virtual Enterprise

Total commitement

Attributablecommitement

Extended Enterprise

(after Russel, ICEM99)

P.Bernus 1999

Performance metrics

• Need ways to derive performance metrics (and attribution of contributions) in the extended enterprise

P.Bernus 1999

New (open) problem of VE modelling

• Need to disclose details to be able to plan and predict (e.g. by simulation) the properties of VE

• Need to preserve key business knowledge

Same contradictioin exists on the person / group and group / enterprise level!

P.Bernus 1999

Requirement

• How to achieve / control

trust

commitment

visibility

P.Bernus 1999

VE as post-matrix

• Cooperation among the same discipline groups in the VE may replace the disciplinary (functional) part of organisation -- needs formal associations (networks, partnerships,..)

P.Bernus 1999

The End

Documents

New Applications Of GERAM to Virtual Enterprises And Networks