web services-based collaborative system for distributed ... · inter-organisational workflows ....
TRANSCRIPT
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, 8-10.09.2008
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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.
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -5-
Infineon’s pan-European distribution
Courtesy:Dr. Matthias Bauer, Infineon Technologies
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -6-
Our motivation for collaborative design
Supporting integration of SMEs into complex design
inter-organisational workflows
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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.
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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
FP6-2004-IST-NMP-2 Project No 016527
09.2005-02.2008
http://mapper.eu.org
PRO-VE’08, Poznań, 8-10.09.2008 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.
PRO-VE’08, Poznań, 8-10.09.2008 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.
PRO-VE’08, Poznań, 8-10.09.2008 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.
Open, visual,
holistic, reconfigurable
collaboration platform
Interoperability
among enterprises’
software and services
SME NEnterprise 1
Interaction and
integration
between human
and technical
resources
Fast, flexible
and inexpensive
deployable
solutions
Software
systems of
company 1
Software
systems of
company N
Collaboration between
enterprises, integration
of products, processes
and services
Open, visual,
holistic, reconfigurable
collaboration platform
Interoperability
among enterprises’
software and services
SME NEnterprise 1
Interaction and
integration
between human
and technical
resources
Fast, flexible
and inexpensive
deployable
solutions
Software
systems of
company 1
Software
systems of
company N
Collaboration between
enterprises, integration
of products, processes
and services
PRO-VE’08, Poznań, 8-10.09.2008 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)
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -17-
Participative engineering methodology
Standard-based Interoperability Framework
(e.g. ATHENA)
Customisable
work
environments
Reconfigurable
POPS* models
Secure service
integration platform
Participative
methodology
Standard-based Interoperability Framework
(e.g. ATHENA)
Customisable
work
environments
Reconfigurable
POPS* models
Secure service
integration platform
Participative
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
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -18-
Standard-based Interoperability Framework
(e.g. ATHENA)
Customisable
work
environments
Participative
methodology
Secure service
integration platform
Reconfigurable
POPS* models
Standard-based Interoperability Framework
(e.g. ATHENA)
Customisable
work
environments
Participative
methodology
Secure service
integration platform
Reconfigurable
POPS* models
• 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.
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -20-
AKM model of a distributed collaborative design realised by two SMEs
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -22-
Secure service integration platform
Standard-based Interoperability Framework
(e.g. ATHENA)
Customisable
work
environments
Participative
methodology
Reconfigurable
POPS* models
Secure service
integration platform
Standard-based Interoperability Framework
(e.g. ATHENA)
Customisable
work
environments
Participative
methodology
Reconfigurable
POPS* models
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.
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -23-
Customizable work environments
Standard-based Interoperability Framework
(e.g. ATHENA)
Participative
methodology
Reconfigurable
POPS* models
Secure service
integration platform
Customisable
work
environments
Standard-based Interoperability Framework
(e.g. ATHENA)
Participative
methodology
Reconfigurable
POPS* models
Secure service
integration platform
Customisable
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
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -25-
MAPPER collaboration infrastructure
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -26-
Layers of Services on Top of AKM
MAPPER approach towards CWE -2-
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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
2003
2005
2006
2007
TRMS development path
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -36-
TRMS 2.0 architecture
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -37-
37
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).
PRO-VE’08, Poznań, 8-10.09.2008 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.
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -39-
39
Tool invoker
• Responsible for:
– Fetching of input data
– Program invocation
– Dispatching of console messages
– Sending of results
• Constant connection with GTLS isn’t required
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -40-
40
Client application
• Two versions: Tiny vs. Fat Client (adminstrator)
• Constant connection with GTLS isn’t required (one may invoke a design task and switch of the client application)
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -42-
42
Used technologies
• Java SE 6
• Apache Tomcat 5.5 (lub 6)
• Apache AXIS 1.3 (lub 2)
• Hibernate
• HSQL (MySQL, PostgreSQL)
• appframework, jdesktop
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 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
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -49-
Active Knowledge Model of common USB PHY
design flow
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -50-
Pilot 3 USB-OTG-PHY design coverage
Analog block Digital block
High Speed
AnalogFront End
HS Receiver
HS Transmitter
Full Speed
AnalogFront End
FS Receiver
FS Transmitter
High Speed
Control Logic
HS Receive logic
HS Transmit logic
Full Speed
Control Logic
FS Receive logic
FS Transmit logic
UTMI+USB lines
USB PHY design
Integration &Verification of whole USB PHY design was a scope of the Pilot 3
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -52-
Pilot 3 infrastructure
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -53-
Pilot 3 – step1 – Digital design + tests
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -54-
Pilot 3 – step 1
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -55-
Pilot 3 – step 2 – Integration of both PHY parts
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -56-
Pilot 3 – step 2
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -57-
Pilot 3 – step 2
Digital waveform view
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -58-
Pilot 3 – step 2
Analog waveform view
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -59-
Pilot 3 – step 3
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -60-
Pilot 3 – step 3
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -61-
Pilot 3 – step 4
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -62-
Pilot 3 – step 4
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -63-
CURE interface
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -64-
CVW interface
PRO-VE’08, Poznań, 8-10.09.2008 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 didn’t 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
PRO-VE’08, Poznań, 8-10.09.2008 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.
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -67-
Acknowledgements
Presented work has been commenced within projects: – E-COLLEG (IST-1999-11746), as well as
– VOSTER (IST-2001-32031), as well as
continued in the - MAPPER project (FP6-2004-IST-NMP-2 016527)
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)
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -68-
68
Available books
CCE’07, Kraków
Preliminary
Workshop
materials
CCE’06,
Prague
AITPL cluster book
with MAPPER
contribution Book published by
GI in Lecture Notes
in Informatics
PRO-VE’08, Poznań, 8-10.09.2008 A. Pawlak SUT, Poland -69-
More information on MAPPER
Joint Call 2 : FP6-2004-IST-NMP-2 (October 14 2004)
Topic: IST-NMP-1 : Integrating Technologies for the Fast and Flexible
Manufacturing Enterprise
Run: 2006.09 – 2008.02 (30 months)
http://mapper.eu.org
comprises:
• TRMS demo
• TRMS documentation
• MAPPER project papers and demonstrations
Thank you for your attention!