Presentation is loading. Please wait.

Presentation is loading. Please wait.

Web services-based collaborative system for distributed engineering Adam Pawlak Paweł Fraś Piotr Penkala * Silesian University of Technology Inst. of Electronics,

Similar presentations


Presentation on theme: "Web services-based collaborative system for distributed engineering Adam Pawlak Paweł Fraś Piotr Penkala * Silesian University of Technology Inst. of Electronics,"— Presentation transcript:

1 Web services-based collaborative system for distributed engineering Adam Pawlak Paweł Fraś Piotr Penkala * Silesian University of Technology Inst. of Electronics, Collaborative Engineering Group Gliwice, Poland also Evatronix SA PRO-VE'08 9th IFIP Working Conference on Virtual Enterprises Poznań, Poland,

2 PRO-VE08, Poznań, A. Pawlak SUT, Poland -2- Outline Collaborative engineering for distributed product development Challenges in collaborative design MAPPER project objectives and approach MAPPER collaborative infrastructure Requirements for distributed tool integration TRMS - Tool Registration and Management Services New TRMS architecture Deployment of TRMS Conclusions

3 PRO-VE08, Poznań, A. Pawlak SUT, Poland -3- is an innovative method for product development which integrates widely distributed engineers for virtual collaboration. [Cutkosky, MADEFAST, Communicat. of the ACM, Sept. 1996] shared eng. data real-time communicat. interactivity Objective: distributed design of the optical seeker Collaborative engineering

4 PRO-VE08, Poznań, A. Pawlak SUT, Poland -4- Why collaborative engineering in electronics Time to market vs design complexity is since ever the most significant factor for new product creation Thus, increase of design productivity is one of the major objectives within the SoC domain resolved by: Structured design methodology with IP design reuse Designing on higher levels of design abstraction Collaborative design is another approach allowing to increase design productivity of electronic systems with : Easy and close collaboration of widely distributed engineers being experts in different domains and in different design flow phases Controlled remote access to expensive design tools, etc.

5 PRO-VE08, Poznań, A. Pawlak SUT, Poland -5- Infineons pan-European distribution Courtesy:Dr. Matthias Bauer, Infineon Technologies

6 PRO-VE08, Poznań, A. Pawlak SUT, Poland -6- Our motivation for collaborative design Supporting integration of SMEs into complex design inter-organisational workflows

7 PRO-VE08, Poznań, A. Pawlak SUT, Poland -7- Selected Challenges in Collaborative Engineering Establishment of an efficient collaborative engineering environment requires solving at least the following problems: Collaboration with organisations protected behind firewalls Data format conformity, etc. Easy tool integration with standard support for : –Tool description –Design task description –Workflow description Secure design data transfer Support for human actors – engineers collaborative actions –Appropriate collaborative workspaces –Advanced synchronous and asynchronous communication

8 PRO-VE08, Poznań, A. Pawlak SUT, Poland -8- SMEs collaboration perspective In this work we take an SME perspective for companies distributed engineering collaboration towards a common product.

9 PRO-VE08, Poznań, A. Pawlak SUT, Poland -9- TRMS - Secure integration of distributed tools Secure integration of distributed design tools was the reserch goal of the Collaborative Engineering group at SUT since ~2000 Architecture of TRMSv1 was the first result achieved withing the EU project ECOLLEG

10 PRO-VE08, Poznań, A. Pawlak SUT, Poland -10- TRMS operation protocol: a: tool registers with profile b: user asks for tool with constraints c: registry checks constraints and returns profile d: user lunches tool with input and output e: tool fetches input and processes output f: destination fetches output Animation l E-COLLEG Tool Registration and Management Services

11 PRO-VE08, Poznań, A. Pawlak SUT, Poland -11- MAPPER context We have addressed our didributed colaborative design problem in the context of the EU project MAPPER MAPPER - Model-based Adaptive Product and Process Engineering FP IST-NMP-2 Project No

12 PRO-VE08, Poznań, A. Pawlak SUT, Poland -12- Problem statement for MAPPER The core problems in the area of faster and more flexible design and manufacturing (agile engineering) concern: –Quick and inexpensive formation of networked manufacturing organisations; –Achieving concurrency in all operations; –Bridging the gaps between heterogeneous knowledge, processes, systems, services, and ways of working; –Support rapid reconfiguration of required processes and products to accommodate diverse and changing needs and opportunities; –New, cross-partner knowledge which continuously created and must be shared, executed on and managed.

13 PRO-VE08, Poznań, A. Pawlak SUT, Poland -13- Challenges in collaborative design Concurrency in all operations, increasing design efficiency and decreasing time-to-market. Quick and inexpensive formation of networked design organisations. Processes and products should be rapidly reconfigured to accommodate diverse and changing needs and opportunities. Change management across the entire design chain requires coordination of individual changes and support for iterative adjustments. Collaborative product, process and service engineering must thus be managed and performed across networked organisations. Integration of tools of remote groups of engineers with adequate for industry solutions for: security, distributed inter- organization workflows, and remote administration of users and tools.

14 PRO-VE08, Poznań, A. Pawlak SUT, Poland -14- The Vision of MAPPER In 2015, agile design and manufacturing companies can inexpensively form collaborative networks and quickly adapt to market demands.

15 PRO-VE08, Poznań, A. Pawlak SUT, Poland -15- Scientific and technological objectives of MAPPER O1: Reconfigurable visual enterprise models of products, processes and other enterprise aspects; O2: Participative engineering methodologies, enabling joint product and process design, interdisciplinary and inter-organisational collaboration throughout multiple product life-cycles; O3: Customisable work environments for different stakeholders, roles and tasks; O4: Secure collaboration platform, enabling enterprises to access each others engineering tools and product data in an open, yet secure manner; O5: To develop and assess three industrial use-cases, and to validate the overall MAPPER approach: - automotive industry (Fiat) and automotive components supplier (Kongsberg Automotive, SWE, N, PL) - electronics industry (IP components supplier, Evatronix, PL)

16 PRO-VE08, Poznań, A. Pawlak SUT, Poland -16- MAPPER approach Standard-based Interoperability Framework Customisable work environments Participative methodology Reconfigurable models Secure service integration platform Integrate enterprise modelling, human-centred methodologies, collaborative customisation, and secure, distributed tool invocation, into an open, visual, holistic, and reconfigurable collaboration platform

17 PRO-VE08, Poznań, A. Pawlak SUT, Poland -17- Participative engineering methodology A method of engineering involving personnel from several areas, possessing different knowledge and skills, responsible for performing various roles in an engineering process. This methodology aims at integrating product, process and service engineering and have the components: –Networked manufacturing enterprise modelling –Formation and operation of sustainable collaboration –Inter-organisational learning –Multi-project portfolio management

18 PRO-VE08, Poznań, A. Pawlak SUT, Poland -18- Active knowledge modelling –An approach used to construct live networked manufacturing enterprise models. –AKMs describe the relevant resources, aspects, views, methods and rules to externalise and facilitate knowledge-driven, adaptive collaboration and learning. Reconfigurable models Visual modelling and visual scenes. –Visual modelling as a more powerful representation means for sense making: in using systems and in modifying systems.

19 PRO-VE08, Poznań, A. Pawlak SUT, Poland -19- Whats AKM - Active Knowledge Modelling Co to jest AKM: Model jest tworzony przez użytkowników realizujących zadanie Modele są dostępne w czasie realizacji (execution time) Wsparcie dla ewolucyjnego współbieżnego modelowania i realizacji Identyfikacja wiedzy o firmie i budowanie konsensusu Pro-aktywne uczenie i budowanie zespołu Wsparcie socjalne i organizacyjne Dlaczego różni się od innych strategii Wzorniki są adaptowalne lub tworzone w czasie modelowania Wspiera modelowanie jako wielowymiarowy proces Umożliwia stosowanie różnych perspektyw Wspiera ewolucję języków modelowania i projektowania AKM musi być wsparty zintegrowaną platformą do modelowania i realizacji modeli Strategie i metodologie muszą być adoptowalne

20 PRO-VE08, Poznań, A. Pawlak SUT, Poland -20- AKM model of a distributed collaborative design realised by two SMEs

21 PRO-VE08, Poznań, A. Pawlak SUT, Poland -21- Why active models ? Representation must be available to the users of the information system at runtime Model must influence the behaviour of the underlying computerised system Model must be dynamic and reconfigurable, users must be supported in changing the model to fit their local reality, enabling tailoring of the system's behaviour Refer to Active Knowledge Modelling at:

22 PRO-VE08, Poznań, A. Pawlak SUT, Poland -22- Secure service integration platform Basic services needed for collaborative enterprise modelling and execution –Modelling services –Model execution services –Collaboration services –Secure tool integration services Secure services-based collaboration platform that enables companies to access shared engineering tools and data on products in a user and secure collaboration friendly way is the goal.

23 PRO-VE08, Poznań, A. Pawlak SUT, Poland -23- Customizable work environments User interfaces integrating all the software and information needed to perform a particular task Packaging functionality according to the user needs and expectations Customisation and contextualisation Flexible work environments adaptable for various partners, roles and tasks The collaborative platform should enable companies offering (e.g. design) solutions and their customers to commonly adapt and configure their work environment

24 PRO-VE08, Poznań, A. Pawlak SUT, Poland -24- Collaboration infrastructure Needed to support networked manufacturing between heterogenous enterprises. Includes information and communication technology Integrates services in the platform Enables sharing of representations of partners technical capabilities and resources

25 PRO-VE08, Poznań, A. Pawlak SUT, Poland -25- MAPPER collaboration infrastructure

26 PRO-VE08, Poznań, A. Pawlak SUT, Poland -26- Layers of Services on Top of AKM MAPPER approach towards CWE -2-

27 PRO-VE08, Poznań, A. Pawlak SUT, Poland -27- Requirements from MAPPER AKM - Active Knowledge Model paradigm Services context from MAPPER Integration within MAPPER collaborative platform Profound requirements engineering process SourceS of requirements: – Evatronix and advICo engineers -Reflections from the SUT R&D team -Ethnografic fields studies at companies sites done by social sciences experts

28 PRO-VE08, Poznań, A. Pawlak SUT, Poland -28- Figure of MAPPER integration platorm

29 PRO-VE08, Poznań, A. Pawlak SUT, Poland -29- Requirements modelling as AKM Requirements from Evatronix modelling in METIS Social scientists were performing ethnographic field studies. Observations and conclusions were assembled in reports that were provided as additional requirements to research & technology teams working on the collaboration infrastructure

30 PRO-VE08, Poznań, A. Pawlak SUT, Poland -30- TRMS 1 E-Colleg result application ANTS transport mechanism partial firewall crossing TRMS 1.1 initial version for MAPPER application own transport mechanism no firewall crossing TRMS 1.2 developed in MAPPER applet own transport mechanism service-based functionality TRMS 2 new architecture application http/https transport mechanisms firewall crossing TRMS development path

31 PRO-VE08, Poznań, A. Pawlak SUT, Poland -31- TRMS - Secure integration of distributed tools Architecture of TRMSv1 – ECOLLEG result

32 PRO-VE08, Poznań, A. Pawlak SUT, Poland -32- TRMS 1.0 Result of the E-Colleg project Application version Limited functionality in the firewalled networks (with ANTS transfer mechanism) User authentication with keys Implemented internal security mechanisms

33 PRO-VE08, Poznań, A. Pawlak SUT, Poland -33- TRMS 1.1 (initial version prepared for MAPPER) Application version No ANTS transfer mechanism ANTS replaced with own developed transfer solution (no firewall crossing, it is not sufficient for pilot 3 needs) Applied in pilot 2 deployment phase (middle 2007)

34 PRO-VE08, Poznań, A. Pawlak SUT, Poland -34- TRMS 1.2 Developed for integration within MAPPER infrastructure New Web services developed Applet version Limited security level and functionality but easier to be integrated Integration with Metis environment

35 PRO-VE08, Poznań, A. Pawlak SUT, Poland -35- TRMS 2.0 motivation Based on experiences with versions 1.x in E-Colleg and MAPPER projects User requirements from Evatronix engineers Limitations of the previous versions Integration needs of MAPPER e-team

36 PRO-VE08, Poznań, A. Pawlak SUT, Poland -36- TRMS 2.0 architecture

37 PRO-VE08, Poznań, A. Pawlak SUT, Poland GTLS Global Tool Lookup Service Responsible for management of elements of the environment and security policy GTLS is the only TRMS component accessible from the Internet Communication broker Client – Tool Invoker GTLS plays a role of a broker and a temporary repository in a communication between a Client Application and Tool Servers. GTLS cooperates with SQL data base DB contains information on users and their privileges, TSs, registered tools, and workflows. (Design) data management Implemented as a set of Web Services (Apache AXIS).

38 PRO-VE08, Poznań, A. Pawlak SUT, Poland -38- GTLS (main) web services Administration Administration services are responsible for registration and modification of data on users and their privileges, elements of the system, as well as, information on accessible tools and machines that make them available. User and Server Authentication Upon user/designer logs in, a new session is created and a user receives its key. Tool Servers are authenticated automatically upon their invocation. Task Management Each tool that is expected to be accessible over the network needs to be registered and placed in the task queue. Registration involves determination of necessary data for tool invocation. Workflow Management A workflow constitutes a set of tasks that are in the task queue. Current implementation supports sequential workflows.

39 PRO-VE08, Poznań, A. Pawlak SUT, Poland Tool invoker Responsible for: –Fetching of input data –Program invocation –Dispatching of console messages –Sending of results Constant connection with GTLS isnt required

40 PRO-VE08, Poznań, A. Pawlak SUT, Poland Client application Two versions: Tiny vs. Fat Client (adminstrator) Constant connection with GTLS isnt required (one may invoke a design task and switch of the client application)

41 PRO-VE08, Poznań, A. Pawlak SUT, Poland -41- TRMS 2.0 new functionality versus versions 1.x Support for work in the networks with NAT and firewalls Communication is always initiated by either tool servers or client applications. Tool server (tool invoker) polls for a job to do. Support for long jobs Client app can be switched off during the job execution on a tool server. Actual job status and output results are available during the consecutive log-in. Support for a sequential workflows Next task is executed under the control of GTLS after the previous one is over. Access to console output messages of the invoked tool A number of users can access and control the execution of a task

42 PRO-VE08, Poznań, A. Pawlak SUT, Poland Used technologies Java SE 6 Apache Tomcat 5.5 (lub 6) Apache AXIS 1.3 (lub 2) Hibernate HSQL (MySQL, PostgreSQL) appframework, jdesktop

43 PRO-VE08, Poznań, A. Pawlak SUT, Poland -43- TRMS 2.0 achievements (technology and architecture) New TRMS architecture is based on Web services thus supporting (MAPPER) integration with other Collaborative Working Environmnts Both applet and application versions are available Secure transmission channel, optional encoding using keys Transfer based on standard https or http protocols Deployed in MAPPER pilots 2 and 3 -(intra-) and inter-company distributed tool integration

44 PRO-VE08, Poznań, A. Pawlak SUT, Poland Security Secure transmission channel Optional encoding using keys Level of user privileges (unix, xwr, group)

45 PRO-VE08, Poznań, A. Pawlak SUT, Poland -45- TRMS 2.0 plans Extend functionality and user interface (e.g., user awareness, event notification service) Development of a more advanced workflow management system

46 PRO-VE08, Poznań, A. Pawlak SUT, Poland -46- USB PHY design challenges in MAPPER –Experts were needed from two different designers worlds: analogue and digital –The design environment is distributed (2 companies, 3 locations) –Problems with interoperability of current design tools (different domains, different file formats) TRMS deployment

47 PRO-VE08, Poznań, A. Pawlak SUT, Poland -47- Evatronix and advICo workflows Component specification Development Verification Product preparation Each company has well defined own design flow advICo Design Flow

48 PRO-VE08, Poznań, A. Pawlak SUT, Poland -48- Distributed design and verification between advICo and Evatronix advICo Design Flow Evatronix Design Flow Analog and Digital Block integration Integration of USB PHY digital and analogue design flows was a problem

49 PRO-VE08, Poznań, A. Pawlak SUT, Poland -49- Active Knowledge Model of common USB PHY design flow

50 PRO-VE08, Poznań, A. Pawlak SUT, Poland -50- Pilot 3 USB-OTG-PHY design coverage Integration &Verification of whole USB PHY design was a scope of the Pilot 3

51 PRO-VE08, Poznań, A. Pawlak SUT, Poland -51- Pilot 3 Distributed design and verification between Advico and Evatronix Demo

52 PRO-VE08, Poznań, A. Pawlak SUT, Poland -52- Pilot 3 infrastructure

53 PRO-VE08, Poznań, A. Pawlak SUT, Poland -53- Pilot 3 – step1 – Digital design + tests

54 PRO-VE08, Poznań, A. Pawlak SUT, Poland -54- Pilot 3 – step 1

55 PRO-VE08, Poznań, A. Pawlak SUT, Poland -55- Pilot 3 – step 2 – Integration of both PHY parts

56 PRO-VE08, Poznań, A. Pawlak SUT, Poland -56- Pilot 3 – step 2

57 PRO-VE08, Poznań, A. Pawlak SUT, Poland -57- Pilot 3 – step 2 Digital waveform view

58 PRO-VE08, Poznań, A. Pawlak SUT, Poland -58- Pilot 3 – step 2 Analog waveform view

59 PRO-VE08, Poznań, A. Pawlak SUT, Poland -59- Pilot 3 – step 3

60 PRO-VE08, Poznań, A. Pawlak SUT, Poland -60- Pilot 3 – step 3

61 PRO-VE08, Poznań, A. Pawlak SUT, Poland -61- Pilot 3 – step 4

62 PRO-VE08, Poznań, A. Pawlak SUT, Poland -62- Pilot 3 – step 4

63 PRO-VE08, Poznań, A. Pawlak SUT, Poland -63- CURE interface

64 PRO-VE08, Poznań, A. Pawlak SUT, Poland -64- CVW interface

65 PRO-VE08, Poznań, A. Pawlak SUT, Poland -65- Distributed design and verification of USB PHY design at advICo and Evatronix Conclusions feedback from companies METIS – models of each company design process allow to develop the best common design process for this special (from each company perspective) USB PHY design CURE – As this interface didnt require any additional effort from end users to setup it, and it can be used almost everywhere where the Internet access is available. TRMS – possibility of invoking it just from web browser, implemented security, remote invocation of different design tools. All these features support automatisation of design processes. TRMS helped Evatronix/advICo to use design tools more efficiently. Finally, it accelerated designers work

66 PRO-VE08, Poznań, A. Pawlak SUT, Poland -66- Conclusions The TRMS architecture based on web services has the following advantages: Enables easier integration with other collaborative environments, GTLS as a communication broker enables use of tools that are installed in local networks on machines that are not visible from outside, The new architecture supports also tools that require long computation times, The environment is robust enough for transient problems in accessing the network, It reduces demand for a broad bandwidth in accessing the network, and speeds up the overall the environment, The use of the standard HTTPS protocol enables control of the network traffic. Further R&D related to TRMS includes enhanced workflow management system and improved support for engineering teamwork with both synchronous and asynchronous collaboration.

67 PRO-VE08, Poznań, A. Pawlak SUT, Poland -67- Acknowledgements Presented work has been commenced within projects : –E-COLLEG (IST ), as well as –VOSTER (IST ), as well as continued in the - MAPPER project (FP IST-NMP ) Wojtek Sakowski and Szymon Grzybek from Evatronix. MAPPER partners are acknowledged for their R&D efforts in respect to the presented collaborative infrastructure. –Dr. Havard Jorgensen (AKM) Oslo, Norway) –Svein G. Johnsen, SINTEF, Oslo (Norway) –Dr. Frank Lillehagen (AKM, Oslo, Norway) –Prof. Kurt Sandkuhl, Jönköping University, Jönköping (Sweden) –Dr. Till Schümmer, FernUniversität Hagen, Hagen (Germany)

68 PRO-VE08, Poznań, A. Pawlak SUT, Poland Available books CCE07, Kraków Preliminary Workshop materials CCE06, Prague AITPL cluster book with MAPPER contribution Book published by GI in Lecture Notes in Informatics

69 PRO-VE08, Poznań, A. Pawlak SUT, Poland -69- More information on MAPPER Joint Call 2 : FP IST-NMP-2 (October ) Topic: IST-NMP-1 : Integrating Technologies for the Fast and Flexible Manufacturing Enterprise Run: – (30 months) comprises: TRMS demo TRMS documentation MAPPER project papers and demonstrations Thank you for your attention!


Download ppt "Web services-based collaborative system for distributed engineering Adam Pawlak Paweł Fraś Piotr Penkala * Silesian University of Technology Inst. of Electronics,"

Similar presentations


Ads by Google