1. P.Bernus 1999 New Applications Of GERAM to Virtual Enterprises And Networks Peter Bernus Griffith University June, 1999

2. P.Bernus 1999 Overview Project enterprise as a Virtual Enterprise Bidding and performing the project Virtual manufacturing / service enterprise Properties of VE

3. P.Bernus 1999 Life-cycle of a OKP (e.g. plant) Design Preliminary design Detailed design Identification Concept Requirements Implementation Operation DecommissionGERA

4. P.Bernus 1999GERA Time Redesign/ refurbish project Plant Operation Life history of a OKP (e.g. plant) Plant engineering and construction project using concurrent engineering Decommissioning project Life-cycle Resource development planning Continuous improvement planning

5. P.Bernus 1999GERA Time Redesign/ refurbish project Plant Operation Competencies Plant engineering and construction project using concurrent engineering Decommissioning project Life-cycle Resource development planning Continuous improvement planning { Company competency Engineering Project Enterprise’s competency { Construction company competency { Plant competency { {

6. P.Bernus 1999 Relationship between life-cycles design preliminary design detailed design identification concept requirements implementation operation decommission operation Project Enterprise PlantGERA

7. 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

8. P.Bernus 1999 Characteristic life history of project enterprise

9. P.Bernus 1999 Contributions to the life-cycle of a OKP (plant) company plant Engineering Contractor Engineering Subcontractors { { { Engineering Project Enterprise Construction Company { Infrastructure providers

10. P.Bernus 1999 Operations Management and Control System Operations Management and Control System Operations Management and Control System Negotiate project Carry out project

11. 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

12. It is the purpose of the design of the management system, to co-ordinate objectives of the high levels with objectives of low levels h=7d p=1d h=1d p=8h h=8h p=1h real time co-ordination

13. P.Bernus 1999 DCs behave as an agent - the challange is for the enterprise as a whole to also behave as an agent (“aware enterprise”)DCs behave as an agent - the challange is for the enterprise as a whole to also behave as an agent (“aware enterprise”) The production management system of one integrated enterprise will achieve this. Problem: how to co-ordinate non incorporated enterprises (virtual enterprises) to achieve the same?The production management system of one integrated enterprise will achieve this. Problem: how to co-ordinate non incorporated enterprises (virtual enterprises) to achieve the same?

14. Traditional value chain is not co-ordinated: the virtual enterprise is not an agent h=7d p=1d h=1d p=8h h=8h p=1h real time co-ordination operational interaction only, feedback fixes only individual problems h=7d p=1d h=1d p=8h h=8h p=1h real time co-ordination

15. Integrated value chain is co-ordinated: the virtual enterprise is an agent multi-level interaction: objectives are co-ordinated on every horizon (also on top!) co-ordination h=7d p=1d h=1d p=8h h=8h p=1h real time h=7d p=1d h=1d p=8h h=8h p=1h real time

16. Consortium with limited co-ordination: the virtual enterprise acts as an agent in a limited domain co-ordination on multiple levels, e.g. joint policy adjustment (in limited domain) co-ordination Here the consortium has separate mgmt with limited authority }

17. 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-ordination H=1y p=3m h=3m p=2w h=2w p=5d real time H=1y p=3m h=3m p=2w h=2w p=5d real time

18. P.Bernus 1999 Based on tender / invitation to bid set up a project to prepare a bid co-ordination H=1y p=3m h=3m p=2w h=2w p=5d real time H=1y p=3m h=3m p=2w h=2w p=5d real time

19. P.Bernus 1999 Allocate resources to bid preparation co-ordination H=1y p=3m h=3m p=2w h=2w p=5d real time co-ordination H=1y p=3m h=3m p=2w h=2w p=5d real time

20. P.Bernus 1999 Question: do we need these strategic / tactical transactions between all partners?

21. Operations Management and Control System Operations Management and Control System Operations Management and Control System Operations Management and Control System Operations Management and Control System The infrastructural service/product providers need not be involved (VE has relative authonomy) VE

22. 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

23. P.Bernus 1999 Necessary competencies Company Plant Engineering Contractor Engineering Subcontractors { { { Engineering Project Enterprise Construction Company { Infrastructure Providers

24. P.Bernus 1999 Time ICRDIODICRDIOD ICRDIODICRDIOD ICRDIODICRDIOD Virtual enterprises Products Network T1T2T3T4 ¶ · ¸ ¹ º » ¼ ½ ¾ ¿ After J.Vesterager, TUD,1999

25. P.Bernus 1999 Necessary competencies Engineering Project Enterprise Design Preliminary design Detailed design Identification Concept Requirements Implementation Operation Decommission

26. P.Bernus 1999 Engineering Project Enterprise Design Preliminary design Detailed design Identification Concept Requirements Implementation Operation Decommission

27. P.Bernus 1999 Plant engineering policies (ISO 9000x) Plant engineering functional requirements specification (STEP) Particular Plant engineering policies Particular Plant Project requirements Function (typical engineering project functions) Information (AP) Resource (Application type) Engineering Project Enterprise Quick to generate in the presence of reference model

28. P.Bernus 1999 Particular Plant engineering policies Particular Plant Project requirements Particular project functions STEP (AP) Selected CAD tool type IDEF0 semantics EXPRESS (language semantics) Resource ontology Engineering Project Enterprise

29. P.Bernus 1999 Project plan (time, cost) Product database design Selected CAD tools, contractors Project mgmt ontology SQL Resource ontology (design level) Engineering Project Enterprise

30. 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

31. 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

32. Operations Material and information flow Supply chain

33. 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 Management and Control System

34. Management and Control System Management and Control System 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

35. 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

36. P.Bernus 1999 Management and Control System Management and Control System Operations End user Not visible for e.u. Management and Control System Management and Control System Operations visible for e.u. End user Virtual Enterprise Total commitement Attributable commitement Extended Enterprise (after Russel, ICEM99)

37. P.Bernus 1999 Performance metrics Need ways to derive performance metrics (and attribution of contributions) in the extended enterprise

38. 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!

39. P.Bernus 1999 Requirement How to achieve / control trust commitment visibility

40. 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,..)

41. P.Bernus 1999 The End