Enterprise Interoperability IV
Keith Popplewell • Jenny Harding Raul Poler • Ricardo Chalmeta Editors
Enterprise Interoperability IV Making the Internet of the Future for the Future of Enterprise
123
Organiser
Promoter
Editors Professor Keith Popplewell Coventry University Future Manufacturing Applied Research Centre CV1 5FB Coventry UK
[email protected] Doctor Jenny Harding Loughborough University Mechanical and Manufacturing Engineering Leicestershire LE11 3TU UK
[email protected]
Professor Raul Poler Polytechnic University of Valencia Research Centre on Production Management and Engineering EPSA Pza Ferrandiz y Carbonell, 2 03801 Alcoy Spain
[email protected] Doctor Ricardo Chalmeta Universidad Jaume I. Av Sos Banyant Grupo de Integración y Re-Ingeniería de Sistemas DLSI s/n 12071 Castellon Spain
[email protected]
ISBN 978-1-84996-256-8 e-ISBN 978-1-84996-257-5 DOI 10.1007/978-1-84996-257-5 Springer London Dordrecht Heidelberg New York British Library Cataloguing in Publication Data A catalogue record for this book is available from the British Library Library of Congress Control Number: 2010923777 © Springer-Verlag London Limited 2010 Apart from any fair dealing for the purposes of research or private study, or criticism or review, as permitted under the Copyright, Designs and Patents Act 1988, this publication may only be reproduced, stored or transmitted, in any form or by any means, with the prior permission in writing off the publishers, or in the case of reprographic reproduction in accordance with the terms of licences issued by the Copyright Licensing Agency. Enquiries concerning reproduction outside those terms should be sent to the publishers. The use of registered names, trademarks, etc. in this publication does not imply, even in the absence off a specific statement, that such names are exempt from the relevant laws and regulations and therefore free for general use. The publisher makes no representation, express or implied, with regard to the accuracy of the information contained in this book and cannot accept any legal responsibility or liability for any errors or omissions that may be made. Cover design: eStudioCalamar, Figueres/Berlin Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com)
Preface Keith Popplewell1, Jenny Harding2, Raul Poler3, Ricardo Chalmeta4 1
2
3
4
Future Manufacturing Applied Research Centre, Coventry University CV1 5FB Coventry (United Kingdom) General Chairperson of I-ESA’10
[email protected] Mechanical and Manufacturing Engineering Loughborough University Leicestershire LE11 3TU (United Kingdom) General co-Chairperson of I-ESA’10
[email protected] Research Centre on Production Management and Engineering Polytechnic University of Valencia EPSA. Pza Ferrandiz y Carbonell, 2, 03801 Alcoy (Spain) Chairperson of the I-ESA’10 International Programme Committee
[email protected] Grupo de Integración y Re-Ingeniería de Sistemas. DLSI. Universidad Jaume I. Av Sos Banyant s/n 12071 Castellon (Spain) co-Chairperson of the I-ESA’10 International Programme Committee
[email protected]
Enterprise Interoperability (EI) is the ability of an enterprise or more generally an organisation to work with other enterprises or organisations without special effort. The capability to interact and exchange information both internally and with external organisations (partners, suppliers, customers, citizens…) is a key issue in the economic and public sector. It is fundamental in order to produce goods and/or services quickly and at lower cost, while ensuring higher levels of quality, customisation, services and security. Today, Enterprises maximise flexibility and speed of response to changing external conditions. They develop knowledge of, and links with, other Enterprises or Organisations with which they can collaborate to provide the products and services that customers demand. The issue of interoperability within the Enterprise is therefore no longer limited to the interoperability between silos of systems within single companies, but has become one of interoperability throughout a Network of Enterprises. I-ESA’10 (Interoperability for Enterprise Software and Applications) is the sixth of a series of conferences, this time under the motto “Making the internet of the future for the future of enterprise”. As Europe and the world focus research on a Future Internet of Things, Services, Knowledge and People, the opportunities for enterprise collaboration are expanding. The focus of interoperability research and
vi
Preface
application is therefore on these opportunities and the new technologies and methodologies needed to exploit the Future Internet to the full. I-ESA’10 reports on current research in this field, as well as the underlying developments in enterprise interoperability which have been the foundation for this domain. The I-ESA’10 Conference was organized by Coventry University and the Virtual Laboratory for Enterprise Interoperability (INTEROP-VLab) and sponsored by the International Federation for Information Processing (IFIP). The world's leading researchers and practitioners in the area of Enterprise Integration from government, industry and academia have contributed to this book. As a result, Enterprise Interoperability IV is a unique anthology presenting visions, ideas, research results, industrial experiences and problems on business interoperability. This book is organized in seven parts addressing the major research in the scope of Interoperability for Enterprise Software and Applications: I II III IV V VI VII
Business Interoperability Enterprise Modeling for Enterprise Interoperability Semantics for Enterprise Interoperability Architectures and Frameworks for interoperability Platforms for Enterprise Interoperability Interoperability Scenarios and Case Studies Standards for Interoperability
Coventry Loughborough Alcoy Castellón April 2010
Keith Popplewell Jenny Harding Raul Poler Ricardo Chalmeta
Acknowledgements
We would like to thank all the authors, invited speakers, International Programme Committee members, International Senior Programme Committee members, Steering Committee members and participants of the conference that made this book a reality and the I-ESA’10 a success. We express our gratitude to all organizations which supported the I-ESA’10 preparation, especially the Virtual Laboratory for Enterprise Interoperability (INTEROP-VLab) and its UK Pole and the International Federation for Information Processing (IFIP). We are deeply thankful to the local organization support notably Joanna Sychta, Muqi Wulan, Mohammad Al-Awamleh and Shagloof Dahkil for their excellent work for the preparation and the management of the conference.
Contents
Part I Business Interoperability Ad-hoc Execution of Collaboration Patterns using Dynamic Orchestration Jean-Pierre Lorre, Yiannis Verginadis, Nikos Papageorgiou and Nicolas Salatge ......................................................................................................... 3 Alternative Process Notations for Mobile Information Systems Sundar Gopalakrishnan and Guttorm Sindre ......................................................... 13 Conceptual Framework for the Interoperability Requirements of Collaborative Planning Process María M.E. Alemany, Faustino Alarcón, Francisco C. Lario and Raul Poler ....... 25 Improving Interoperability using a UML Profile for Enterprise Modelling Reyes Grangel, Ricardo Chalmeta, Cristina Campos and Sergio Palomero ......... 35 Towards Test Framework for Efficient and Reusable Global e-Business Test Beds Nenad Ivezic, Jungyub Woo and Hyunbo Cho ....................................................... 47 Unified Reversible Life Cycle for Future Interoperable Enterprise Distributed Information Systems Zhiying Tu, Gregory Zacharewicz and David Chen ............................................... 57 Part II Enterprise Modeling for Enterprise Interoperability A Meta-model for a Language for Business Process Characterizing Modelling Shang Gao and John Krogstie ................................................................................ 69
x
Contents
A Tool for Interoperability Analysis of Enterprise Architecture Models using PiOCL Johan Ullberg, Ulrik Franke, Markus Buschle and Pontus Johnson ..................... 81 A UML-based System Integration Modeling Language for the Application System Design of Shipborne Combat System Fan Zhiqiang, Gao Hui, Shen Jufang and Zhang Li .............................................. 91 Contribution to Interoperability of Executive Information Systems Focusing on Data Storage System Guillaume Vicien, Yves Ducq and Bruno Vallespir .............................................. 101 GRAI-ICE Model Driven Interoperability Architecture for Developing Interoperable ESA Lanshun Nie, Xiaofei Xu, David Chen, Gregory Zacharewicz and Dechen Zhan......................................................................................................... 111 Model for Trans-sector Digital Interoperability António Madureira, Frank den Hartog, Eduardo Silva and Nico Baken ............. 123 Transformation from a Collaborative Process to Multiple Interoperability Processes Hui Liu and Jean-Pierre Bourey .......................................................................... 135 Part III Semantics for Enterprise Interoperability A Manufacturing Foundation Ontology for Product Life Cycle Interoperability Zahid Usman, Robert I.M. Young, Keith Case and Jenny A. Harding ................. 147 A Semantic Mediator for Data Integration in Autonomous Logistics Processes Karl Hribernik, Christoph Kramer, Carl Hans and Klaus-Dieter Thoben .......... 157 An Ontology Proposal for Resilient Multi-plant Networks Rubén Darío Franco, Guillermo Prats and Rubén de Juan-Marín ...................... 169 Collaboration Knowledge Ontologies to Support Knowledge Management and Sharing in Virtual Organisations Muqi Wulan, Xiaojun Dai and Keith Popplewell ................................................. 179 Mediation Information System Engineering for Interoperability Support in Crisis Management Sébastien Truptil, Frédérick Bénaben, Nicolas Salatgé, Chihab Hanachi, Vincent Chapurlat, Jean-Paul Pignon and Hervé Pingaud.................................. 187 Service Value Meta-Model: An Engineering Viewpoint Zhongjie Wang, Xiaofei Xu, Chao Ma and Alice Liu ........................................... 199
Contents
xi
Part IV Architectures and Frameworks for interoperability An Interoperable Enterprise Architecture to Support Decentralized Collaborative Planning Processes in Supply Chain Networks Jorge E. Hernández, Raul Poler and Josefa Mula ............................................... 213 Business Cooperation-oriented Heterogeneous System Integration Framework and its Implementation Yihua Ni, Yan Lu, Haibo Wang, Xinjian Gu and Zhengxiao Wang ...................... 225 Collaboration Knowledge Management and Sharing Services to Support a Virtual Organisation Muqi Wulan, Xiaojun Dai and Keith Popplewell ................................................. 235 Developing a Science Base for Enterprise Interoperability Yannis Charalabidis, Ricardo J. Goncalves and Keith Popplewell ..................... 245 From Pipes-and-Filters to Workflows Thorsten Scheibler, Dieter Roller and Frank Leymann ....................................... 255 Risk Sources Identification in Virtual Organisation Mohammad Alawamleh and Keith Popplewell..................................................... 265 Service-based Model for Enterprise Interoperability: Context-Driven Approach Alexander Smirnov, Tatiana Levashova and Nikolay Shilov ................................ 279 Transformation of UML Activity Diagram to YAWL Zhaogang Han, Li Zhang and Jimin Ling ............................................................ 289 Part V Platforms for Enterprise Interoperability Gap Analysis of Ontology Mapping Tools and Techniques Najam Anjum, Jenny Harding, Bob Young and Keith Case ................................. 303 Networked Enterprise Transformation and Resource Management in Future Internet Enabled Innovation Clouds Brian Elvesæter, Arne-Jørgen Berre, Henk de Man and Man-Sze Li................... 313 Opportunity Discovery Through Network Analysis Alessandro Cucchiarelli and Fulvio D’Antonio ................................................... 323 Reflections on Aspects of Enterprise Interoperability Jane Hall and Klaus-Peter Eckert ........................................................................ 331 Specification of SETU with WSMO Wout Hofman, Menno Holtkamp and Michael van Bekkum ................................. 341
xii
Contents
Part VI Interoperability Scenarios and Case Studies A Success Story: Manufacturing Execution System Implementation Albin Bajric, Kay Mertins, Markus Rabe and Frank-Walter Jaekel .................... 357 Enabling Proactive Behaviour of Future Project Managers Georgios Kapogiannis, Terrence Fernando, Mike Kagioglou, Gilles Gautier and Collin Piddington ................................................................................................. 367 Gaps to Fill Between Theoretical Interoperable Quality and Food Safety Environment and Enterprise Implementations David Martínez-Simarro, Jose Miguel Pinazo Sánchez and Raquel Almarcha Vela.......................................................................................... 377 How to Develop a Questionnaire in Order to Measure Interoperability Levels in Enterprises Noelia Palomares, Cristina Campos and Sergio Palomero ................................. 387 Knowledge Sharing and Communities of Practices for Intra-organizational Interoperability Philippe Rauffet, Catherine Da Cunha and Alain Bernard .................................. 397 Part VII Standards for Interoperability Aligning the UEML Ontology with SUMO Andreas L. Opdahl ............................................................................................... 409 Emerging Interoperability Directions in Electronic Government Yannis Charalabidis, Fenareti Lampathaki and Dimitris Askounis ..................... 419 Enterprise Collaboration Maturity Model (ECMM): Preliminary Definition and Future Challenges Juncal Alonso, Iker Martínez de Soria, Leire Orue-Echevarria and Mikel Vergara....................................................................................................... 429 Towards a Conceptualisation of Interoperability Requirements Sihem Mallek, Nicolas Daclin and Vincent Chapurlat ......................................... 439 Use Profile Management for Standard Conformant Customisation Arianna Brutti, Valentina Cerminara, Gianluca D’Agosta, Piero De Sabbata and Nicola Gessa......................................................................................................... 449 Index of Contributors ........................................................................................... 461
Part I
Business Interoperability
Ad-hoc Execution of Collaboration Patterns using Dynamic Orchestration Jean-Pierre Lorre1, Yiannis Verginadis2, Nikos Papageorgiou2 and Nicolas Salatge1 1 2
EBM WebSourcing, 4 rue Amélie, Toulouse, France Institute of Communications and Computer Systems, National Technical University of Athens, 9 Iroon Polytechniou Str., Athens, Greece
Abstract. Industrial enterprises realize that in order to function and survive in constantly changing grounds, they need to collaborate dynamically by forming network-based collaborative alliances of a temporary nature. During such collaborations, several segments of work can be often identified as recurring and be reused. The exploitation of this repetition is considered to be critical for these environments, so approaches that propose the use of Collaboration Patterns (CPats), seen as loose workflows of services, can be proven valuable. In this paper we present the use of CPats in virtual organizations that are executed in an ad hoc way. We propose a schema that combines the initiatives of CPats along with a dynamic service orchestration engine based on an autonomic framework called Fractal. Such approach allows reorganizing service workflow at run-time in order to take into account collaboration network plasticity. Keywords: Collaboration pattern, SOA, dynamic service orchestration, BPEL
1. Introduction Modern industrial enterprises as complex and dynamic management systems can be considered as a myriad of concurrent processes executed by a huge set of technological or human entities. In a competitive market environment, these enterprises cope with critical challenges, in order to survive, by trying to establish efficient collaborative mechanisms that may even span their intra-organizational frontiers. The basic motivation behind the necessity of collaborating network enterprises is the intention of exploiting new business opportunities, delivering superior quality products and services and at the same time keeping the production cost as low as possible [1] [2]. Enterprises often realize that the single enterprise model is no longer sufficient to cover all aspects of their needs and try to take part in enterprise collaborative formations referred to as virtual organizations (VOs) [3], [4], [5]. In a virtual
4
J.P. Lorre, Y. Verginadis, N. Papageorgiou and N. Salatge
organization, the participating firm is no longer a physical entity with a stable mission. Instead it is a dynamic entity systematically involved in temporary alliance via networks structures [6]. In such dynamic and virtual but legally consolidated schemas, the arising collaboration issues are considered to be of critical importance. In these challenging environments there is a need for adapting the ways of collaboration in order to reflect the current conditions. A way to address this challenge is by identifying and appropriately reusing Collaboration Patterns (CPats). CPats are segments of collaboration work, which can be identified as recurring and can be reused [7]. The reuse of CPats can constitute an advantage in collaborative environments such as VOs, as there is an increased need for modeling, executing, monitoring and supporting the dynamic nature of collaborations. The overall aim of using CPats is to enable adaptivity and ad hoc realization of collaborations with respect to changing circumstances. In the Service Oriented Architecture (SOA) context, executive forms of CPats is formalised in the BPEL (Business Process Execution Language from the OASIS standardisation body) orchestration language that describe how VOs partners collaborate thanks to a set of services. Consequently, in order to introduce ad hoc nature in terms of run-time collaboration we propose to use the Maestro dynamic orchestration engine that allows process instance re-organization. The main contributions of the paper are the following. First, the paper in section 2 introduces and presents the demanding nature of collaboration patterns along with the proposed use of Maestro for adequately supporting the ad hoc nature that the solution of CPats must present. In section 3 we focus on our CPat execution proposition that involves fractal-based “Maestro” engine for supporting ad hoc workflow executions. In section 4, we give an illustrative scenario of the execution aspects of a specific CPat. Finally, this paper concludes with the related work (section 5) and a discussion that concludes our research effort, in section 6.
2. Collaboration Patterns 2.1. The Demanding Nature of Collaboration Patterns The notion of collaboration involves the complex nature of vast number of processes that may span across organizational/geographical boundaries, through the World Wide Web. The need for coping with iterative problems or reusing iterative segments of collaboration processes (Collaboration Patterns) seems more imperative than ever before. In general, the participants of a collaboration process need to be collocated either physically or virtually in order to make a decision or work together. During such collaborations, recurring segments of solutions to problems or individual actions can be identified and introduced as CPats for future use [7]. These patterns can also be regarded as prescriptive, providing means for modeling collaborative tasks and protocols of cooperation [8], while they can guide
Ad-hoc Execution of Collaboration Patterns using Dynamic Orchestration
5
the configuration of Collaborative Working Environments to meet the requirements of the participants [9], [10]. Among the important elements that are needed for describing a CPat are the triggering mechanisms and the actual solution that they propose [7]. In terms of a system for handling knowledge based collaborations inside VOs, services may produce many events that might be relevant for other services. It is clear that all these influences, due to their ad-hoc nature, cannot be defined in advance explicitly, but they can be categorized and used as triggering mechanisms of recurring segments of collaborative work. In addition, a CPat determines the basic structure of the solution to a particular collaborative problem, while it does not always specify a fully detailed solution. A pattern provides a scheme for a generic solution to a family of problems, rather than a prefabricated module that can be used ‘as is’. The implementation of this schema must be done according to the specific needs of the design problem at hand. CPats are not only useful to users within the same domain as the pattern, but frequently a pattern is useful in other domains as well. As CPat execution we define first the retrieval and instantiation of the appropriate CPat for the collaboration situation (e.g., problem, preconditions, triggering mechanisms), [7] and second the execution of the CPat by the appropriate “execution engine” (e.g., workflow engine, groupware tool, human tasks, etc.). 2.2. SYNERGY Collaborative Framework CPats are used in the context of SYNERGY FP7 research project that defines a collaboration framework based on Service Oriented Architecture concepts. Even if it is not the aim of this paper to detail it, figure 1. depicts main building blocks. It consists of an Event Driven Architecture build on top of the Petals Enterprise Service Bus (ESB). Events are managed at the bus level while Complex Event Processing (CEP) engine allows identifying business events that match event patterns. CPats are triggered by those business events thanks to the CPat assistant which is in charge of selecting corresponding CPat from the CPat Knowledge Base CPat assistant also initializes the Ad-hoc workflow engine which is mainly in charge of executing the proposed by the CPats solution to collaborative problem. Collaboration Moderator Service is in charge of raising awareness of the priorities and requirements of other contributors while the Partner Knowledge Management Service (PKMS) provides effective mechanisms to manage and utilise all the knowledge in the SYNERGY Knowledge Bases.
6
J.P. Lorre, Y. Verginadis, N. Papageorgiou and N. Salatge
CPat editor
CEP editor
CPat Knowledge Base
Event Type Knowledge Base
CPat assistant
Collaboration Moderator Service
Partner Knowledge Management Service
CEP engine Ad-hoc workflow engine Event manager (pub/sub)
Enterprise Service Bus SYNERGY Portal
Fig. 1. SYNERGY technical architecture
2.3. Maestro Workflow Engine for Collaboration Patterns Ad-hoc workflow engine leverage the Maestro BPEL engine that takes into account dynamicity requirement stated previously. Maestro engine is an Enterprise Service Bus (ESB) component able to orchestrate services based on BPEL 2.0 language. An ESB is a standard-based integration platform that combines messaging, Web services, data transformation, and intelligent routing to reliably connect and coordinate the interaction of significant numbers of diverse services across extended enterprises with transactional integrity [11]. Once deployed, services are available inside the ESB or they can be exported outside the ESB. When the BPEL service receives a request, it starts a new instance of corresponding CPat solution. Maestro Engine is basically composed of two layered components (Figure 2): •
Maestro-core which is in charge of creating and executing abstract PetriNet instances (e.g an instance of process). These instances are composed of classical elements existing in Petri-Net framework (node, transition, etc.). Maestro-core is the basis for multiple process languages. Native support for any process language can be build on top of such Petri-Net Virtual Machine. The runtime behavior of each activity in the process graph is delegated to a dedicated API (Application Programming Interface). Each process language deals with specialization of a set of activity types. An activity implements the runtime behavior and corresponds to one activity type. So, building a process language on top of the Maestro-core is as easy as creating a set of activity implementations. Each activity is then inserted
Ad-hoc Execution of Collaboration Patterns using Dynamic Orchestration
•
7
in a node of the objects graph. This is realized by using the Maestro4BPEL interpreter as detailed below. Maestro4BPEL interpreter traduces the BPEL description (e.g. tag elements like <process/>,
etc.) into objects managed by Maestro-core (e.g. petri-net objects like process, node, transition). At the end of this step, an objects graph is built, which contains a set of nodes. Each node (except initial node and end nodes) is highly coupled with incoming and outgoing transitions. An execution object is also created. This object follows the step by step execution of objects graph. If a node has several outgoing transitions, the parent execution creates several child executions to follow each branch.
Fig. 2. Maestro Engine Framework
Dynamicity of BPEL process instances is obtained by basing Maestro-core on the Fractal component model, which means that each Petri-net node and transition has been reified into Fractal component. The Fractal component model [9], [12] is a programming-language-independent component model, which has been introduced for the construction of highly configurable software systems. The Fractal model combines ideas from three main sources: software architecture, distributed configurable systems, and reflective systems. From software architecture, Fractal inherits basic concepts for the modular construction of software systems, encapsulated components, and explicit connections between them. From reflective systems, Fractal inherits the idea that components can exhibit meta-level activities and reify through controller interfaces part of their internal structure. From configurable distributed systems, Fractal inherits explicit component connections across multiple address spaces, and the ability to define meta-level activities for runtime reconfiguration. 2.4. Related Work Within the domain of cross-organizational collaboration, patterns have been mainly used to facilitate the modeling and enactment of inter-organizational business processes [13]. In the domain of Communities of Practice (CoP) task patterns have
8
J.P. Lorre, Y. Verginadis, N. Papageorgiou and N. Salatge
been proposed, mainly in a theoretical level, to define which information patterns are to be created in particular steps of collaboration [14]. Collaboration Engineering (CE) is a research-based approach that aims to provide repeatable, tool-based processes, consisting of elementary items called thinkLets to model recurring collaborative tasks but from the point of view of a meeting facilitator [15]. Petri Nets have been used to model workflows for many years [16]. Others have proposed the π-calculus as a workflow model [17]. Control flow patterns [18] along with data flow [19] and resource patterns [20] have been proposed in order to assess the capabilities of the different workflow technologies, languages and models. To our opinion all of these approaches are too strict and not appropriate for collaborative processes which incorporate knowledge-based, and thus very difficult to prescribe, tasks. On the other hand, UAM method introduces activity patterns [21] in order to facilitate the reuse of ad-hoc collaborative activities and provides all the necessary underlying technologies to achieve that. Where it seems to be weak is in the modeling of complex, structured and event-based processes since the flow of the actions is modeled only as a list or a tree of activities with no constraints. Other approaches focus mainly in the extraction of patterns from collaborative systems with ad-hoc characteristics [22]. Our goal is to address the specificity frontier of collaboration support systems [23], i.e. to support a range of collaboration types, from fixed to ad-hoc. In this respect, our work extends research on activity patterns [21] and proposes CPats as a type of design patterns applicable on event-based systems [24].
3. Maestro Reorganisation Patterns As explained before, since Maestro-core is based on Fractal component model, it enables reconfiguration of running process instances. In this aim, Maestro-core provides a factory containing several reorganization patterns such as convert Flow to Sequence, convert If to Flow etc. Figure 3. depicts the logic and the component representation of the reorganization pattern used to convert flow control instruction into a sequence control instruction. In the component representation, each component is either a node with a functional behaviour like Flow, Sequence, Invoke, If, etc. or a transition with non-functional behaviours like log, persistence, etc. A node can have incoming or outgoing transitions, a parent node and child nodes. A Flow control instruction is represented in our component architecture by a component (or a node) with a Flow behaviour. This behaviour allows the execution in parallel of all child nodes of the flow component (node N2 and N3 on figure 3). All child nodes in the Flow control instruction are executed by a different thread. A Sequence control instruction is represented by a component with a Sequence behaviour. This behaviour allows the execution starting the first child node of the sequence component (node N2 on figure 2). All child nodes in the Sequence control instruction are executed in the creation order in the same thread.
Ad-hoc Execution of Collaboration Patterns using Dynamic Orchestration
9
The used algorithm to achieve the conversion of the flow control instruction into a sequence control instruction is straightforward (read the component representation from right to left): 1. Change the flow behavior of the component by the sequence behavior. Thus, instead of executing all child nodes of the component, only the first child node is executed. 2. Add a transition (T) between node N2 and node N3. Thus, when the activity of node N2 is finished, the node N3 is executed. When the node N3 is achieved, the sequence component activity is finished, so, the node N4 is started.
Figure 3. Reorganization patterns: Flow to Sequence
All these reorganization patterns are contained in the API of the Maestro factory. This factory can be used by the CPat run-time services to reorganize one or several running process instances.
4. Scenario In this section, we give an example of how we can use and execute CPats using the Maestro ad-hoc workflow engine for allowing the modification of the actions described by the CPat solution at the CPat instantiation phase (e.g., modify a sequence of actions from sequential to parallel, delete an action, add an new action etc.). The CPat of our example deals with the case in which a VO member decides to run and support a meeting after a project review has taken place. In the following table we present the specific CPat along with the most important aspects of its description.
10
J.P. Lorre, Y. Verginadis, N. Papageorgiou and N. Salatge Table 1.
CPat
Name:
Category:
Business Pattern
Problem:
Discuss the work progress and the results of a project review.
VO lifecycle phase:
Any
Pre-Conditions:
X (variable) number of VO members available
Triggers: Triggers of Exceptions: Roles: Input Information:
No.
CPat 1
(Meeting Organiser decides to schedule a meeting) AND (Project review completed) One or more VO members report unavailability at last moment (variable) VO Meeting Organiser, VO members / Meeting Participants Project’s DoW (Description of work), VO members’ contact details, EU guidelines, Review Report 1.
Solution:
Involves an action list: a. Meeting Organiser schedules the meeting (describe reason, propose date) b. Meeting Organiser selects meeting participants c. All meeting participants agree upon the meeting date and method (online or offline) d. Meeting Organiser prepares and sends a draft agenda. e. …
2.
Output Information:
Involves the usage of collaborative tools: ¾ engage with collaboration tool (e.g. www.doodle.ch) to find date based on collaborators’ availabilities ¾ virtual collaboration space… Meeting minutes document
Duration:
X (variable) Days
Exception:
Post- Conditions: Related CPats:
Meeting took place, Agreed meeting minutes stored in the system, Reason for having the meeting resolved CPat
The proposed CPat solution involves a set of actions to be undertaken by the VO meeting organizer and the VO members that will participate. We note that the CPat solution constitutes only a “possible” sequence of actions. CPat 1 involves the sequential execution of several actions. This structure is flexible to change when the CPat is being instantiated in order to satisfy the requirements of a particular situation. In our case, during instantiation phase, the VO meeting organizer decides that it would be much more appropriate to start CPat 1 by having action “d” executed in parallel with action “a”, instead of executing the several actions defined in the CPat solution in sequence. Maestro engine undertakes this flow transformation task by applying the “Sequence to Flow” reorganization pattern.
Ad-hoc Execution of Collaboration Patterns using Dynamic Orchestration
11
5. Conclusion This paper presents a framework for running ad-hoc collaborative patterns. Such patterns encapsulate reusable frames of collaboration activities. The approach uses a dynamic orchestration engine, Maestro, which leverages the Fractal component model in order to allow reorganization of flow in the proposed CPat solutions. Modification is managed by the collaboration pattern assistant [7] that triggers the need for reorganization and by Maestro-core that provides a library of reorganization algorithms. The virtual organizations as collaborative environments with increased needs can be favoured by the combined strength of collaboration Patterns and the dynamic nature of the Maestro engine. We believe that this proposal can cope with the critical challenges that a VO environment poses. Further work will be carried out in terms of implementing this framework into event driven environments for validating it across real case scenarios in VOs lifecycles. Our intention is to also use, test and validate CPats in an even broader environment, such as virtual breeding environments or in plain collaboration environments which are situated outside the borders of virtual organizations. Finally, we believe that it will be very interesting to examine ways to use CPats, in order to deal with unanticipated exceptions, that may occur in dynamic collaborative environments.
6. Acknowledgements This work has been partially funded by the European Commission regarding the project SYNERGY (Supporting highlY-adaptive Network Enterprise collaboration thRouGh semanticallY-enabled knowledge services), ICT No 63631. The authors would like to thank the project team for comments and suggestions.
7. References [1] [2] [3] [4] [5] [6] [7]
Fox MS. Issues in enterprise modeling. Systems, Man and Cybernetics, 'Systems Engineering in the Service of Humans', Conference Proceedings, vol. 1, pp. 86-92, 1993. Matos C, Afsarmanesh H. Collaborative Networked Organization: A research agenda for emerging business models, Springer Press, 2004. Davidow WH and Malone MS. The Virtual Corporation. Harper-Collins, New York, 1992. Mowshowitz A. Virtual Organization. ACM 40, 9 (Sept. 1997), 30–37. Mowshowitz A. Virtual organization: A vision of management in the information age. Inf. Soc. 10 (1994), 267–288. Ahuja MK, Carley KM. Network Structure in Virtual Organizations, Organization Science, v.10 n.6, p.741-757, June 1999 Verginadis Y, Apostolou D, Papageorgiou N, Mentzas G. Collaboration Patterns in Event-Driven Environment for Virtual Organisations. Intelligent Event Processing –
12
[8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24]
J.P. Lorre, Y. Verginadis, N. Papageorgiou and N. Salatge Association for the Advancement of Artificial Intelligence (AAAI) Spring Symposium 2009, Stanford, USA Molina, A. and Bell R. A Manufacturing Model representation of a flexible manufacturing facility. Journal of Engineering Manufacture: Proceedings of the Institution of Mechanical Engineers 213(B), 1999, pp. 225-246. Bruneton E., Coupaye T, Leclercq M., Quema,V. and Stefani JB. The Fractal Component Model and its Support in Java. Software - Practice and Experience 2006; 36:11-12. Slagter R, Biemans M. and Jones VM. Service Orchestration for Collaboration Patterns. Technical Report TR-CTIT-05-71, Centre for Telematics and Information Technology, University of Twente, Enschede, ISSN 1381-3625, 2005. Chappell D. Enterprise Service Bus: Theory in Practice, O'Reilly Media, 2004. Merle P., Stefani JB. A formal specification of the Fractal component model in Alloy. INRIA research report No 6721, 2008. Norta A., Hendrix M. and Grefen P. A Pattern-Knowledge Base Supported Establishment of Inter-organizational Business Processes. R. Meersman, Z. Tari, P. Herrero et al. (Eds.): OTM Workshops 2006, LNCS 4277, 2006, pp. 834–843. De Moor, A. Community Memory Activation with Collaboration Patterns. Proceedings of the 3rd International Community Informatics Conference (CIRN 2006) Prato Italy, pp. 1. Briggs, R. O. Collaboration Engineering with ThinkLets to Pursue Sustained Success with Group Support Systems. Journal of Management Information Systems, 19, 3164, 2003. van der Aalst, W. M. P. The Application of Petri Nets to Workflow Management. JOURNAL OF CIRCUITS SYSTEMS AND COMPUTERS, 8, 21-66, 1998. Puhlmann, F. & Weske, M. Using the pi-Calculus for Formalizing Workflow Patterns. LECTURE NOTES IN COMPUTER SCIENCE, 3649, 153, 2005. van der Aalst WMP, ter Hofstede AHM, Kiepuszewski B. and Barros AP. Workflow Patterns. Distributed and Parallel Databases, 14(3), 2003, pp. 5–51. Russell N, ter Hofstede AHM, Edmond D. and van der Aalst WMP. Workflow Data Patterns. Technical report, (FIT-TR-2004-01), 2004a. Russell N., ter Hofstede AHM, Edmond D. and van der Aalst WMP. Workflow Resource Patterns. BETA Working Paper Series, WP 127, Eindhoven University of Technology, 2004b. Moody P, Gruen D, Muller MJ, Tang J. and Moran TP. Business activities patterns: a new model for collaborative business applications. IBM Systems Journal 45(4), 2006, pp. 693-694. Biuk-Aghai R. Patterns of Virtual Collaboration in Online Collaboration Systems. Proceedings of the IASTED International Conference Knowledge Sharing and Collaborative Engineering, ACTA Press, 2004, pp. 57-62. Bernstein A. How Can Cooperative Work Tools Support Dynamic Group Processes? Bridging the Specificity Frontier, CSCW’00, Philadelphia, PA, 2000. Paschke A. Design Patterns for Complex Event Processing. 2nd International Conference on Distributed Event-Based Systems (DEBS'08), 2008.
Alternative Process Notations for Mobile Information Systems Sundar Gopalakrishnan1 and Guttorm Sindre1 1
Department of Computer and Information Science, Norwegian University of Science and Technology (NTNU), Sem Sælands vei 7-9 , NO-7491 Trondheim Norway
Abstract. Model-based requirements specifications may be performed using a wide variety of notations, emphasizing different standards and information needs. Most of these notations have been developed with more traditional information systems development in mind, not specifically for mobile information systems. While many of the same modelling approaches will be relevant for mobile information systems, too, there are reasons to believe that the modelling needs in that domain might be somewhat different. In particular, the location and context of an information processing activity will be less fixed than for a desktop-based system, and this may also cause a bigger need for modeling this location and context. This paper explores some alternative notation variants for UML activity diagrams to address these needs. Some notations are proposed and compared, using a case study from the home care domain. Keywords: Requirements specifications, model-based, UML, use case diagrams, BPMN
1. Introduction A large number of diagrammatic modeling techniques have been used in information systems analysis and requirements engineering, such as goal modeling [1] conceptual modeling [10], and process modeling [4] including UML, use cases [11] and BPMN. For requirements specification [5] [6], there exist different diagrammatic modeling languages typically to address a lot of different aspects [7], such as • • •
WHAT (information is supposed to be handled by the system, e.g., in terms of classes and relationships) HOW (is the system going to solve its tasks, e.g., in terms of process models) WHEN (are tasks going to be performed, e.g., shown in more precise process models including timing)
S.Gopalakrishnan and G. Sindre
14
• •
WHY – in terms of goals or business rules WHO – in terms of agents / roles. Some languages typically combine WHY and WHO, such as i* or Kaos [3]
For mobile information systems another question emerges, namely WHERE? Most naively this can be considered in a purely geographical sense – where is a certain activity supposed to be performed or a certain service supposed to be offered? However, it can also be considered from a multi-channel [12] point of view – through which kind of equipment is the functionality going to be offered? [13] [14] Or from the point of view of the working context: In what situation is the user when needing the functionality, e.g., is it going to be used in a car, and is the car standing still or driving, and in the latter case: is it the person driving the car who actually needs to use the system at the same time? All this may have important bearings on the requirements and later design of the system, and would therefore be relevant to capture in early stage system models. This paper is organised with related works in section 1.2, proposed diagram notation in section 1.3 followed by evaluation in section 1.4, conclusion and with possible future work in section 1.5.
2. Related Works The Volere specification approach [8] provides a general template for all kind of requirements, but as mentioned earlier mobile requirements specification is unique and could not specify the “where” aspect. RE techniques mostly uses diagrams for requirements and visual notations play important role in all engineering disciplines. The works carried out in MPOWER project [17] uses UML notations in their home care system extensively and concludes UML profiles can be used as a mechanism for toolchains based on OMG’s Model Driven Architecture(MDA) and UML standards[16]. Larsson [7] proposes the three building blocks for knowing the processes list How, What and Why, adds Who for use oriented design approach and omitted the ‘Where’ concept. Veijalainen [15] mobile ontologies development identifies the ‘where’ aspect, but excludes the ‘what’ aspect.
3. Proposed Diagram Notation With the background of Home care system [9] case study, consider the simple UML [2] activity diagram in Fig. 1. A brief summary of home care system is given below: The shift leader is responsible for the work at the zone, answering to Trondheim municipality. Nurses typically have more somatic knowledge than the home care assistants, and are to support social needs. The home care assistants typically work more broadly work with personal care before lunch, and then with home care (i.e. practical tasks in the home). The diagram in Fig. 1 typically focuses on HOW the process is performed (the activity boxes and decision diamonds) and by WHOM (swimlanes, typically roles in the organization). WHAT could be included by rectangles representing information objects manipulated by the activities (not done here for the sake of
Alternative Process Notations for Mobile Information Systems
15
simplicity). WHY is not so much included in this type of diagram, but could be addressed in another type of diagram, for instance a goal hierarchy. The WHERE dimension is typically not included in this type of diagram. Since the process is about home care and the loop indicates that the home care assistant is visiting multiple patients during the day, one could make the guess that the assistant might need to drive a car or use some other kind of transportation to get around to the various clients, but this is not explicit in the model. However, this could be interesting both for understanding the process and for discussing potential improvements. For instance, when it comes to understanding: -
Is the activity “Get preparatory information about patient” performed while in office (i.e., before going to see the patient), during transportation, or at the patient’s home? Similarly, is “Log info about visit” performed at the patient’s, upon returning to the car, or when returning to the office?
Fig. 1. Example UML activity diagram for a home care process
And, when it comes to possible improvement: -
Assuming the assistant currently returns to the office after each patient, which increases the drive time and makes for a less efficient process –
16
S.Gopalakrishnan and G. Sindre
-
-
how to distinguish this diagrammatically from the other alternative of only returning to the office after visiting all patients? Assuming that the assistant currently makes temporary logs on paper, which then have to be transcribed electronically after the visiting round – how to distinguish this from the practice of logging electronically while at the patient’s or in the car, using mobile equipment? Assuming that the shift leader wants more flexibility, e.g., dynamically reallocating patients between different assistants, either based on assistant capacity (for instance, one assistant might end up using extra time with one patient due to some complications, thus not having time for all patients on her list, while another assistant might have available capacity) or based on patient availability (e.g., one patient is not available for home care for a certain period of the day because she needs to go to the dentist or whatever, and therefore wants to be rescheduled). This could be achieved by communicating interactively with the assistants while they are on their rounds, but this would require the use of mobile equipment and necessary documentation about patients being available through that equipment, rather than assistants having received the needed documentation on paper prior to their rounds.
For both these main purposes (process comprehension and process improvement) it could be worthwhile to look into notations which explicitly show WHERE a task is performed, in what context, and with what equipment. Here we will explore various ways to do this: -
attempt A: using existing notation as-is, just adding some explanatory annotation attempt B: redefine the usage of swimlanes attempt C: using color or other notation to indicate WHERE-aspects
In Fig. 2 the first approach is illustrated. The diagram is largely the same as we just showed, only that some annotational boxes have been added where appropriate. Also, it is clearly shown where the activities of the home care assistant are performed and under what conditions. This would be important input to further requirements work, for instance knowing that preparatory info about the patient should be possible to acquire while driving the car, the system must be able to provide this info to the home care assistant as audio, either from mobile equipment or equipment belonging to the car, since if the assistant has to use his hands or eyes a lot to get the info, this could interfere with safe driving. A possible disadvantage of these annotations is that they might clutter up the diagram with a lot of extra nodes. In the next diagram another approach is shown, redefining the usage of swimlanes. Now, these are no longer used for indicating the organizational WHO but instead to show WHERE. For WHO, stick figures are used instead, since this is more consistent with some other diagram types in UML (e.g., use case diagrams). However, this diagram has another disadvantage, namely that a lot of edges are needed to indicate who performs which task, especially for the “Homecare assistant” who performs most of the tasks. Hence, Fig. 3 looks a lot messy and worse than Fig. 2 at this point. An attempt to mend it is shown in Fig. 4, where the parenthesis “all other activities” is added
Alternative Process Notations for Mobile Information Systems
17
to the name of the Homecare assistant actor, so that the connecting lines can be dropped. In addition to the mentioned parenthesis, the stick figure for the HCA is also made bigger to indicate that this is the prime actor of the process. However, this would only work nicely if there is one particular actor who is responsible for most of the activities in a diagram. If there are several actors each responsible for a number of activities, it would be impossible to avoid the mess of a lot of edges.
Fig. 2. Home care example with annotations showing place and context
18
S.Gopalakrishnan and G. Sindre
Fig 3. Home care example with redefined swimlanes
Fig. 4. Attempt to improve on Fig. 3
Another idea could be the use of colour, such as in Fig. 5 (a).
Alternative Process Notations for Mobile Information Systems
19
The disadvantage is that a colour legend has to be established, but if the same colours are then used consistently over a number of modelling projects, this will be a small investment, and gradually it might be less needed to have the legend visible in every diagram. Alternatively there might just be a link to the legend so that it could be accessed if needed. Another advantage of the color version, as illustrated in Fig 5 (b) is that if several process design alternatives are put side by side, it becomes very easy to quickly spot differences in planned locations of activities. The reader would see almost immediately that the only differences between the two diagrams is that the prep info and logging activities are performed in different places (car vs. office, car vs. patients’ home). This notation might therefore be particularly useful for easily discussing alternative process designs by means of location. Also, since the use of colors means that one avoids to add extra nodes (in contrary to the annotation variant) or extra edges (with the stick figure actor variant), diagram complexity is not so much increased here, except the reader must of course understand the usage of the colors. Alternatively patterns can be used instead of colours. It is of course possible to illustrate differences between process design alternatives by the other approaches, too. But for the annotation version Fig. 2 in particular this would be a lot more subtle, the differences only being shown as different texts within annotation rectangles, therefore needing close inspection of the model to be discovered by the user. Another possible advantage of color is if there are different options for how to perform an activity, e.g., if the worker has a personal choice whether to do the prep info activity in office or while driving the car. With the color approach, this could easily be shown by having two different colors inside the node for that particular process step, again easy for the reader to spot quickly and not increasing diagram complexity that much as shown in Fig.6.
5 (a)
5 (b) Fig 5. Example using color
20
S.Gopalakrishnan and G. Sindre
Fig. 6. Including an optional choice of location for a process step
4. Evaluation In this paper we used the home care system [9] at Trondheim city in Norway as a case study. The UML diagram notations presented in section 1.3 is based on a simple task in the complete home care system. It is regarded more important to understand alternate notations in view with mobile information systems than presenting the whole scenario of mobile care system. Before evaluation of these notations it is necessary to understand the some information about mobile care system at Trondheim [9]. The home care involves services being offered in the home of the customer, including practical help and home nursing care. In the ‘Mobile Care’-project, it is planned to better support the mobile aspects of the home care service by providing the employees continuous access to Gerica and other relevant systems from wherever they are using a PC/PDA-solution. This is seen in connection to the ‘Wireless Trondheim’-project, which is currently building a mobile broadband for Trondheim. In other parts of Trondheim, one so far has only UMTS or GPRS coverage (i.e. with lower bandwidth for data transfer). The 4 alternate process notations presented in section 1.3 just reflect the same task by home care assistant who visits patients according to the list given by shift leader. Using Gerica on PDA, the home care assistant logs the info about patients on the go intimating patient health status to the nurse at hospital receive further
Alternative Process Notations for Mobile Information Systems
21
info about the logs. By Fig. 1 notations, these tasks performed can be understood but it lags the information where it is done. Also it hard to make dynamic log change for example the shift leader wants to prioritise patients schedule could not reflect in this notation. Fig. 1 notation is not reflecting the state of art use of mobile technologies in home care system. In Fig. 2, the notations are better than Fig. 1 comparatively to have where the tasks are carried out. At the cost of extra nodes in Fig. 2, where the activities and under what conditions has notified. But these extra nodes will be disadvantage if the same notation is used to represent entire home care system. The swim lanes and stick diagrams are representing where and who respectively in Fig. 3. This notation has a disadvantage of lot of edges on who performs the tasks can be overcome by assigning HCA to all other activities as in Fig. 4. Keeping a colour legend and assigning consistently through modelling project is performed by notation in Fig. 5. This notation seems to be simple and easy to perform a large project for example home care system provided a colour legend established and used consistently throughout the project. The same notation is improved in Fig. 6 showing optional choice of performing tasks. On using patterns instead of colour, certainly patterns have an advantage with respect to colour-blindness, on the other hand patterns might be slightly more difficult to distinguish quickly, especially if there are many locations/contexts that must be differentiated between so that one has to use many different patterns, which would make them more subtle and therefore require closer inspection of the model. With the annotation approach it could be described in text in the rectangle, e.g., “In office or while driving to patient’s home, according to worker’s preference” – easily understandable but needing closer inspection to spot. (and also causing annotation texts to be longer, which might mean that rectangles would have to be bigger, thereby cluttering up the diagram more, etc.). With the swimlane + stick figure approach, it gets very hard to illustrate such optional choices. Of course, an activity could be put on the boundary between two swimlanes, but this will only work if the alternative locations are actually on adjacent swimlanes. In other cases, one would simply have to put occurrences of the same activity step in several swimlanes and perhaps indicating the choice with a decision diamond, which would increase the diagram complexity quite a lot. Also, it might overload the decision diamond if this is used both for decisions concerning what to do, and decisions concerning where to do it. Table 1. Evaluation of proposed notations with simple and large models Notation
Trad. UML Annotated Loc.Swimlanes Loc.Swiml. with big actor colours Colours with optional choice
Min. deviation from standard Simple Large
Expressiveness
Intuitive / Easy to read Simple Large
Less Complexity
Simple
Large
Simple
Large
++ + -
++ + -
-+ +
-+ +
++ -
++ ---
++ + +
++ ---
-
-
+
+
-
--
+
-
-
-
++ ++
++ ++
+ +
+ +
++ ++
++ ++
S.Gopalakrishnan and G. Sindre
22
Table 2. Evaluation of proposed notations with SEQUAL framework Notation
Traditional UML Act. Diag. Annotated Location Swimlanes Loc. Swim. with big actor colours Colours with opt. choice
SEQUAL Framework on Language Quality Organizational Appropriateness
Domain Appropriateness
Comprehensibility Appropriateness
+ + + + ++ ++
+ + + + ++ ++
++ ++ + ++ ++
In Table 1, the proposed notations for small and large models are evaluated against four key features viz, minimal deviation from standard, expressiveness, intuitive/ easy to read and less complexity of models. In Table 2, by using SEQUAL framework, the notations are evaluated against its language quality viz, organizational, domain and comprehensibility appropriateness.
5. Conclusion and Future Work This paper analyse all the stated notations including the standard UML activity diagram and proposes alternate possible notations to specify mobile information systems. This specification analysis is performed with simple model in home care system starting with with UML activity diagram notation. The same is carried out with different alternate possible notations so that it can completely provide informations on what, who, how, why and where aspects and evaluated in the above section. Although to some extent it can be realised that some diagrams are better or worse than others, e.g., that Fig. 3 is a way too messy, empirical investigations are needed to make strong conclusions about what ideas are worth pursuing. Evaluation results are tabulated in Table 1 and 2 concluding colours and colours with optional choice have more positive features than other proposed notations. A wide range of different experiments can be envisioned where competing notations are compared to each other and the different notations would not have to be UML either, they could also be based on other modelling languages.
6. References [1] [2] [3]
Mylopoulos, J., Chung, L., and Tu, E., From Object-oriented to Goal-oriented Requirements Analysis Communications of the ACM. 1999,42(1): 31-37. Zhu, L. and I. Gorton, UML Profiles for Design Decisions and Non-Functional Requirements, in Proceedings of the Second Workshop on Sharing and Reusing architectural Knowledge Architecture, Rationale, and Design Intent. 2007, IEEE CS. Oliveira, A.d.P.A., et al., Integrating scenarios, i*, and AspectT in the context of multi-agent systems, in Proceedings of the 2006 conference of the Center for Advanced Studies on Collaborative research. 2006, ACM: Toronto, Ontario, Canada.
Alternative Process Notations for Mobile Information Systems [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]
23
Pavlovski, C.J. and J. Zou, Non-functional requirements in business process modeling, in Proceedings of the fifth on Asia-Pacific conference on conceptual modelling - Volume 79. 2008, Australian Computer Society, Inc.: NSW, Australia. Ohnishi, A. Software requirements specification database based on requirements frame model in Requirements Engineering, Proc. of the 2nd Int. Conference on. 1996. Mujumdar, S., et al., A model-based design framework to achieve end-to-end QoS management, in Proceedings of the 43rd annual Southeast regional conference Volume 1. 2005, ACM: Kennesaw, Georgia. Larsson, A. V., Designing for use in a future Context – Five Case Studies in Retrospect, PhD thesis No:1034, 2003, Institute of Tech., Linkoping Univ., Sweden. URL: http://www.volere.co.uk/template.htm, accessed on 7th Dec 2009 URL: http://research.idi.ntnu.no/trimaks, accessed on 7th Dec 2009 Sølvberg, A., Data and what they refer to, in P.P.Chen et al. (eds.): Conceptual Modeling, 1999, pp.211-226, Lecture Notes in Computer Science, Springer Verlag. Booch, G., Rumbaugh, J. & Jacobson, I., “The Unified Modeling Language: User Guide Addison-Wesley, 1999. URL: http://m3w.idi.ntnu.no/ accessed on 7th 2009 Gopalakrishnan, S. and Sindre, G., Taxonomy of Mobility-Related Requirements", IEEE CS(I-ESA'09), Beijing, China, 20-22 Apr, 2009. Gopalakrishnan, S. and Sindre, G., A Revised Taxonomy of Mobility-Related Requirements, In Proc. International Workshop on Management of Emerging Networks and Services (MENS'09), St.Petersburg, Russia, 12-14 Oct, 2009 Veijalainen, J., Developing Mobile Ontologies; who, why, where, and how? IEEE, 07. Moody,D.L., The “Physics” of Notations: Towards a Scientific Basis for Constructing Visual Notations in Software Engineering. IEEE Transanctions on Software Eng. 09. Walderhaug, S., Stav, E. and Marius Mikalsen, M., Experiences from Model-Driven Development of Homecare Services: UML Profiles and Domain Models, LNCS 2009.
Conceptual Framework for the Interoperability Requirements of Collaborative Planning Process1 María M.E. Alemany1, Faustino Alarcón1, Francisco C. Lario1, Raul Poler1 1
Research Centre on Production Management and Engineering (CIGIP), Polytechnic University of Valencia, Camino de Vera s/n, Valencia 46022, Spain
Abstract. In order to achieve the multiple benefits of the collaborative planning (CP) process in a supply network (SN) context, some interoperability-related obstacles should be saved. The design and characterization of the CP process is a critical time to identify not only the interoperability requirements (IR), but also the CP components they affect. This paper presents a conceptual framework for the simultaneous characterization of the CP process and the identification of the potential IR to be saved for implementing collaboration. This early IR identification can help define the interoperability problem space that is essential for the solution space definition, thus saving subsequent costs and efforts. Keywords: collaborative planning process, supply networks, conceptual framework, interoperability requirements
1. Introduction Collaborative Planning (CP) is defined as a joint decision-making process for aligning the plans of individual Supply Networks (SN) members for the purpose of achieving coordination (adapted from [1]). Coordination should be achieved between the plans of SN decision-makers at different temporal levels (temporal integration) and at the same temporal level (spatial integration). Different authors strength the importance of analysing the collaboration under a process perspective [2;3] and the necessity of making processes inter-operable to achieve the collaboration benefits [4]. [5] affirm that the first step to give solutions
1
This research has been partially carried out in the framework of a Subproject funded by the Science and Technology Ministry of the Spanish Government, entitled PSS-370500-20063 "SP3 Integración operativa de la Cadena de Suministro.", within the project PSE370500-2006-1.
26
MME Alemany, F Alarcón, F.C. Lario, and R. Poler
for making a process inter-operable is the identification of the interoperability requirements (IR). In this context, [6] propose a framework for the classification and a methodology for collection of the requirements for enterprise modelling interoperability. [7] propose a framework able to handle the diversity of collaborative processes based on different computational and communication requirements. [8] describe how to connect internal processes of two companies supported by the cross-organizational business process meta-model. [9] present a framework and general requirements for seamless interoperability in a collaborative network environment. Different tools, ICT platforms, reference models, frameworks [10;11] and its evaluation for interoperability have been proposed. However, up to our knowledge, there is no any conceptual framework for CP focusing on the process perspective and, additionally, addressing the interoperability issue. Though works have been identified that tackle with the interoperability issue, they are mainly focused on classifying the IR and analysing existing interoperability solutions much more than on reporting when? and where? the potential IR could appear along the process. Even more, there has not been found any work linking the IR with the specific CP process. Being identified this gap in the literature, this paper proposes a conceptual framework for the CP process characterization that allows the IR identification during the design of the CP process, in a structured way. The process design and analysis is a critical phase for the early IR identification and the latter search for interoperability solutions, thus saving later costs and efforts. The paper is structured as follows. The next section details the components of the CP conceptual framework and their relationship with the IR. The last section provides some conclusions relating the applicability and benefits of the proposal.
2. Description of the CF Components for the CP Process: Identification of IR The conceptual framework of this paper presents the same fundamental components as those proposed by [12], but with two main differences: 1) the contents of each element of the conceptual framework refer to the CP process and not to the Collaborative Order Promising Process, and 2) special attention has been paid to the IR in each element’s description. The IR are based on those proposed by [10; 9; 13] in a collaboration context and have been completed by the authors. These IR requirements have been classified using the interoperability levels (data, services, processes and business) proposed by INTEROP NoE for the enterprise interoperability framework [10]. A process will be defined when the answers to questions (a)-(g) are known (Table 1). The answer to each question corresponds with the characterization of a conceptual framework component which is described and linked with the IR in this section (Table 2).
Conceptual Framework for the IRs of Collaborative Planning Process
27
Table 1. Components of the conceptual framework THE PROCESS ITSELF
THE INFORMATION
(a) What activities are to be carried out? (b) Who is responsible, who has the authority to carry them out and with what? (c) When and how are they to be carried out?
EVALUATION ASPECTS
(d) The process inputs,
(f) The process objectives,
(e) The process outputs,
(g) The performance indicators
Table 2. Relationship among each CF component and the IR INTEROPERABILITY Levels of Interoperability
Interoperability Requirements
What activities?
PROCESS ITSELF
INFORMATION REQUIREMENTS
Who and with what?
Process Inputs & Outputs
When and How?
EVALUATION ASPECTS (Ex ante) Objectives
(Ex post) Performance Indicators
Modes of decision-making [10] Alignment of conflicting objectives and goals Methods of work [10] Definition of domain of decisions and actions
BUSINESS
Agreement in responsibility and authority Learning Compatibility of organizational structure Integrated evaluation of inter-organizational activities and processes Base-detailed level of business representation [13] Definition and specification of the inter-organizational collaborative activities [10]
PROCESS
Business documents choreography [9] Definition of the interdependence information Achieve the roles/tasks fulfilment [9] Identification of potential activities to be automated
SERVICE
Linking applications and services addressing aspects related to interfaces, ICT platforms [9] Messaging (communication and message format) [9] Data integration [10] Information exchange [10] Semantics of the exchanged information [9] Format of the exchanged information [9] Information detail
DATA
Accessibility to reliable and real-time information [9] Update of information Management of the stored information [9] Security (confidentiality, authentication, non-repudiation) [9] Business documents formats and contents [9]
Tools and methods used in different companies in the four areas of interoperability concerns (data, services, processes, businesses) should be identified and compared, and their compatibility assessed. The answers to the questions of table 3 could be used as a validation principle for determining if an IR should (a “yes” answer) or not (a“no” answer) be omitted [14]. Table 3. IR validation principles [14] • •
CONCEPTUAL COMPATIBILITY
ORGANIZATIONAL COMPATIBILITY
TECHNOLOGICAL COMPABITIBILITY
Syntactic: is the information to be exchanged expressed with the same syntax? Semantic: does the information to be exchanged have the same meaning?
•
•
•
Persons: are authorities/ responsibilities clearly defined at both sides? Organization: are the organization structures compatible?
•
Platform: are the IT platform technologies compatible? Communications: do the partners use the same protocols of exchange?
28
MME Alemany, F Alarcón, F.C. Lario, and R. Poler
2.1. The Collaborative Planning Process What activities have to be carried out? The activities in such a process are dependent on the level of detail adopted for its representation and, therefore, the answer to the subsequent questions ((b)-(c)) is conditioned by the first question (a). Indeed, to achieve the inter-organizational IR integration process, the selection of a specific language for the business process description and the methods to link the disjointed view of the processes are essential, particularly in terms of the level of detail [13]. Therefore, to integrate the different planning sub-processes of each organization at the different CP temporal levels, we identified a base-detail level process representation that considers a base-activity as a set of activities for a specific temporal level of the CP process that: 1) has the same function, 2) has to be considered simultaneously (executed in the same planning period and at the same time point) given their strong interdependency and 3) has the same responsible party. In the following section we refer to the base-activity. The following main CP activities classification, based on the function performed, are proposed: • •
•
•
•
Initial and final activities: these activities determine when the process should be initiated and finalized, respectively. Planning activities: through their execution, a decision related to the SN Planning function is performed (i.e., to generate a production plan). To define them, the IR decision-making modes, the IR working methods, and the definition of the IR domain and decisions need to dealt with. Initial plan generation activities: these are in charge of generating an initial solution to start a negotiation process, should it exist. To define them, the IR decision-making modes, the IR working methods, and the definition of the IR domain and decisions need to be dealt with. Call activities: are in charge of making the execution of other activities possible. At the base-level business representation adopted, it usually links activities from the planning activities belonging to different responsible parties and/or organizations. They are essential in achieving all the IR related with messaging such as communication, message format, business document format, security, etc. Information Management Activities: they refer to those activities where either some type of information transformation, mainly due to spatial or temporal integration, or a calculus based on previous information, is made: o
spatial integration: at the same temporal level it would be necessary to pass information in the appropriate form to other SN members (e.g., to calculate the total requested supply quantity to each producer’s facility from the distributor’s distribution plan expressed as a vehicle and a facility).
o
temporal integration: as one moves down the decision-making temporal hierarchy, planning horizons shorten and the granularity of the information used increases in such a way as to permit the explicit representation and the timing of the key events [15]. Then, it would be necessary to
Conceptual Framework for the IRs of Collaborative Planning Process
29
aggregate/disaggregate the information relating to time, items and resources exchanged among the activities belonging to the different temporal levels. These types of activities are essential to solve the IR data integration, the semantics of the IR information exchanged, the availability of the IR information, and managing the IR information stored. •
Conditional activities: they check the accomplishment of certain conditions. Depending on whether these conditions have been achieved or not, the subsequent activities to be triggered differ. Conditional activities are essential for implementing the negotiation process and its finalization, and also for harmonizing the different decision-making modes and the IR working methods.
The above classification of activities could be useful for the definition and specification of inter-organizational IR collaborative activities. An interorganizational activity may be considered to link activities whose responsible party belongs to different organizations, and/or that the part of the physical SN under its control belongs to different organizations. Furthermore, the above classification linked with the answer to “with what?” can help in the identification of potential activities to become automated IR. Who is responsible to perform each activity and with what? Once the activities to be carried out in the CP process has been clarified: responsibility for their execution, authorizations and computer applications that could be of use in the decision-making process should all be defined. We distinguish four main categories of responsible parties (Table 4). A mediator is an additional SN member who controls the rules of the negotiation process, e.g., controlling the (timing of) interactions among members. A mediator may have the capability to evaluate the SN members’ plans, generate plans and present them to all the SN members for their evaluation, or propose the distribution of efficiency gains among SN members. For other activities than the planning type ones, another part or application will be defined as their responsible parties. The definition of responsibilities is strongly dependent on the SN organization and decision characteristics; however it is possible to provide some guidelines (Table 4). Table 4. Relationships among the different types of activities and those responsible RESPONSIBLE/ ACTIVITIES Planning Initial plan generation Call Information management Conditional
Planning decision-maker
Mediator
Another part
Application (automated)
At this point the compatibility of the IR organizational structures should be addressed. Furthermore, the definition of the responsible parties of the planning activities depends on the characteristics of the physical, decision and organization scope of these activities. The physical, decision and organization scope of each activity will allow the definition of the decisions and actions (IR) domain. The designation of responsibility for each activity will contribute to achieve the IR roles/tasks fulfillment. Furthermore, the specification of IR responsibility and
30
MME Alemany, F Alarcón, F.C. Lario, and R. Poler
authority is essential in defining IR security (confidentiality, authentication, non repudiation) and accessibility to IR information (authorization). Conditional activities require the IR related to negotiation specifications and collaborative agreement to have been previously defined. Therefore, the IR of available business documents for this type of activities has to be dealt with. Regarding the answer to the question with what?, it may be stated that planning activities and initial plan generation activities are usually supported by applications based on simulation, heuristic or mathematical programming models, which are partly automated because they require their responsible party’s validation. The remaining CP activities can be easily automated. Therefore in this step, not only the IR of linking applications and services addressing aspects related to interfaces, ICT platforms, exchange and accessibility, security and standards. but also those in relation to harmonizing the different IR decision-making modes and working methods will be addressed. When must CP activities be done? The execution of an activity depends on whether it is period-driven or eventdriven. Although planning activities are usually period-driven (i.e., executed at predefined time intervals, namely the re-planning period) due to temporal integration, they require a previous execution of the planning activities belonging to higher temporal levels that transmit them shared information. Furthermore, when negotiation takes place to achieve spatial integration, planning activities can be executed several times in the same re-planning period until the stopping negotiation criteria are achieved. Therefore, when negotiations among different planning activities take place their timing can be considered a mixture of perioddriven and event-driven activities. It is recommendable that all the planning activities belonging to the same temporal decision level present the same re-planning periods. Therefore, SN members must agree about the most suitable re-planning period for the CP process (IR decision-making modes and working methods). Every time an activity is performed, the information to be exchanged with other IR activities, accessibility to reliable and real-time IR information and IR information updating will be achieved. Finally, the timing of CP process activities is essential in specifying the sequence in which the business documents and information are exchanged in each inter-organizational activity (IR business documents choreography) and the instant when accurate information should be available (IR accessibility). 2.2. Information Requirements Information constitutes the input and output of the CP process. Additionally for the CP process, knowing the local or private information (i.e., not shared information with other activities), and the global or interdependent information (i.e., information shared with other activities) for each activity becomes specially relevant for defining collaboration. The local information of an activity always constitutes an information input or output of the whole process, while part of the global information can remain only as internal flow.
Conceptual Framework for the IRs of Collaborative Planning Process
31
The information to be exchanged among the different CP process activities constitutes one of the pillars for constructing links among inter-organizational subprocesses and requires the IR of the data level. So the first task in solving the IR related to the data level consists in identifying and defining this interdependent information. Furthermore, the information required and generated by an activity strongly depends on the previously specified IR modes and decision-aid tools for decision-making, the working methods employed and the definition of the IR decisions and actions domain. Therefore, there is a bi-directional relationship between these two last aspects that should be evaluated to adjust them both simultaneously. Identifying the required information for it to be shared can facilitate the later implementation of tightly coupled information technology and standards for information interchange. Furthermore, it is essential for establishing the following IR: communication, message format, business documents formats and contents, security, semantics of the information exchanged, managing the information stored, information availability, etc. Information Requirements for Planning and Initial Plan Generation Activities A planning activity attempts to obtain the value of its decision variables (output) that simultaneously optimize or achieve a satisfactory result of an objective/criteria (output) and respect the different limitations based on the available information (input). In table 5 a description of the input and output information of this planning activities is presented. Table 5. Input & output information of planning and initial plan generation activities INPUT INFORMATION Parameters or Data Local Parameters * Private attributes of the planning elements belonging to the system of the planning activity (e.g. costs, capacity, times, etc.) Interdependent Parameters *Shared attributes of the planning elements belonging to the system of the planning activity (e.g. demand forecasts). It is known as information sharing [8]. * Output information of other activities: ÆFrom planning activities: values of the decisions and/or criteria of its planning problem (interdependent decision variables and criteria). It is known as joint decisionmaking [8]. - Spatial integration - Temporal integration Æ From other planning activities
OUTPUT INFORMATION Tentative or Definitive Plan Local Decision Variables/Criteria * Private Decision Variable/Criteria: they are the decision variables/criteria values once executed the planning activity and solved the planning problem that are are not transmitted to other activities. Interdependence DecisionVariables/Criteria *Interdependent Decision Variable/ Criteria: they are those decision variables/criteria values which, in some way, are passed to other activities. This output data becomes input data for others activities, more specifically they become interdependent parameters of other planning activities. Æ Final Decision Variables/Criteria: their values cannot be changed under any condition during the negotiation process or, simply, because there is no negotiation. ÆNon-Final Decision Variables/ Criteria: their values can be modified during the negotiation process: -Temporal integration: disaggregation of decisions for being implemented(e.g. production volume of families should be disaggregated referred to articles) - Spatial integration: their values are adjusted before reaching the stopping criteria of the negotiation process (e.g. ordered/supplied quantities)
Input information of a planning activity refers to parameters and represents known characteristics or properties of SN entities (i.e., capacity of a facility, production cost of an item, etc.), or a relationship among them (processing times of an item on a facility). The interdependent parameters derived from the output decisions of other planning activities belonging to the upper temporal levels or the same temporal levels constitute the links for achieving temporal and spatial integration, respectively. The Output Information of a planning activity is usually integrated by the values of its decision variables and its criteria, and can be partly transmitted to
32
MME Alemany, F Alarcón, F.C. Lario, and R. Poler
other activities, thus becoming the input data (interdependence parameters) for those activities. Identifying the IR of update information is of special relevance to know whether the decision variables of an activity for each negotiation cycle are final or non final. The updating of non final decision variables has to be done for each negotiation cycle until the collaborative agreement specifications have been achieved. It is clear that the IR accessibility to interdependence information should be allowed for at least the responsible party of all the activities implied during the interaction cycle. Information requirements for Management Activities The input information for Management Activities relates with the level of the information detail required for the rest of activities, the format and the IR semantics. These activities collect the interdependence output information of other activities and transform it into the required format for the interdepence input information of other activities, thus achieving spatial and temporal integration. Information requirements for Conditional Activities Input information for conditional activities mainly consists in specifications regarding the collaborative agreement and output information (interdependence variables and/or criteria value) of other activities. Output contains information about whether a condition is accomplished, usually if the stopping negotiation criteria is reached. Depending on the result obtained, the subsequent sequence of activities to be triggered differs. 2.3. Evaluation Aspects Objectives (ex-ante evaluation) Objectives relate with the CP process goals. For collaborative processes, we can distinguish between the CP process objectives as a whole and the activity objectives. In this step, a consensus should be reached among the often conflicting IR objectives of the different SN members under the responsibility of different activities to achieve interoperability at the IR business level. •
•
The CP process objectives can be of three main types [1]. a) alignment of SN material flows, b) search for the SN optimum and c) search for a fair solution consisting in the evaluation of the SN solution as a whole with regard to the desired solution for each SN member. Objectives of activities depend on the type of activity being considered: Planning Activities and Initial Plan Generation Activities Objectives usually consist in simultaneously optimizing the local and interdependence criteria. If the responsible party is a mediator, the objectives of each SN member should be adequately integrated to accomplish the SN objectives as a whole. Conditional activity objectives relate with the accomplishment of a pre-defined criterion. The most usual criteria are the achievement of a pre-defined number of negotiation rounds, an aspiration deviation among the interdependence decision variables for the other SN members (e.g., ordered and supplied quantities), or/and the fairness evaluation of the SN members.
Conceptual Framework for the IRs of Collaborative Planning Process
33
Performance Indicators (ex-post evaluation) Performance indicators are essential to discover to what extent the established objectives are being fulfilled for each SN member and for the entire SN. The definition of the proper SN performance indicators and their threshold could allow the integrated evaluation of inter-organizational activities and IR processes. Once they have been defined, the information required to calculate them must be accessible and updated (accessibility to reliable and real-time IR information). The most usual CP process performance indicators relate to [16]: a) costs (inventory, production, warehousing and transportation costs), b) times (production operation and transport times), c) customer service level (stock out quantities and backorder quantities and d) volume flexibility.
3. Conclusions This paper presents a conceptual framework for simultaneously characterizing both the CP process and the potential IR to be saved for each component of the process. This research attempts to contribute in the alignment of the specific CP business process in the networked organizations, through guiding in the task of making the different SN planning sub-processes interoperable. Interoperability requires the identification of the shared elements and possible barriers between them [14] that is the main objective of this paper. In this sense, enterprise modelling can help identify the IRs trhough the modeling of interactions and information exchanges that occur in collaborations. The detection of IR can be used as a first step for models measuring interoperability through maturity models and other models [14] and determinining the impact of interoperability investments on business [17]. The latter selection of IRs to be solved should help achieve the optimal level of interoperability [18]. At this moment, the framework is being validated trough an application to a ceramic tile supply chain. Future research lines should be focus on a more exhaustive IR identification and the procurement of specific solutions for different IR supported by a methodology.
4. References [1] [2] [3] [4] [5]
Stadtler H. (2009) A framework for collaborative planning and state-of-the-art, OR Spectrum 31 ( 1): 5-30 Osório A.L., Camarinha-Matos L.M. (2008) Distributed process execution in collaborative networks. Robotics and Computer-Integrated Manufacturing 24: 647– 655. Camarinha-Matos L.M., Afsarmanesh H., Galeano N., Molina A. (2009) Collaborative networked organizations – Concepts and practice in manufacturing enterprises. Computers & Industrial Engineering 57: 46–60. Xu H, Koh L, Parker D. (2009) Business processes inter-operation for supply network co-ordination. International Journal of Production Economics 122(1):188-99. Mykkänen, J.A; Tuomainen M.P. (2008) An evaluation and selection framework for interoperability standards, Information and Software Technology 50: 176–197.
34 [6] [7] [8] [9] [10] [11] [12] [13] [14]
[15] [16] [17]
[18]
MME Alemany, F Alarcón, F.C. Lario, and R. Poler Ducq Y, Chen D, Vallespir B (2004) Interoperability in enterprise modelling: requirements and roadmap. Advanced Engineering Informatics 18(4):193-203. Osorio AL, Camarinha-Matos LM. (2008) Distributed process execution in collaborative networks. Robotics and Computer-Integrated Manufacturing 24(5):64755. ATHENA, , (2005) D.A2.2: Specification of a Cross-Organisational Business Process Model, Version 1.0", ATHENA IP, Deliverable D.A2.2. Chituc, C. M.; Azevedo, A.; Toscano, C. (2009) A framework proposal for seamless interoperability in a collaborative networked environment, Comput. Ind. 60(5): 317338. Chen D., Doumeingts G., Vernadat F. (2008) Architectures for enterprise integration and interoperability: Past, present and future, Comput. Ind. 59(7): 647-659 Chen D, Doumeingts G (2003): European initiatives to develop interoperability of enterprise-basic concepts, framework and roadmap, Annual Reviews in Control 27: 153–162. Alarcón F, Alemany MME, Ortiz A. (2009) Conceptual framework for the characterization of the order promising process in a collaborative selling network context. International Journal of Production Economics, 120(1):100-114. O'Brien W. J., Hammer J., Siddiqui M., Topsakal O. (2008) Challenges, approaches and architecture for distributed process integration in heterogeneous environments, Adv. Eng. Inform 22(1): 28-44. Chen D., Vallespir B., Daclin N. (2008) An Approach for Enterprise Interoperability Measurement. Proceedings of the International Workshop on Model Driven Information Systems Engineering: Enterprise, User and System Models (MoDISEEUS'08) Montpellier, France. 1-12 Muckstadt J. A., Murray D. H., Rappold J. A., Collins D. E (2001): Guidelines for Collaborative Supply Chain System Design and Operation, Inform. Syst. Front. 3 (4): 427-453. Beamon B. M., Chen V. C. P, (2001) Performance analysis of conjoined supply chains, Int. J. Prod. Res. 39 (14): 3195-3218. Lebreton, B., Legner, C. (2007) Interoperability Impact Assessment Model – Framework and Application. In Goncalves, R. J., Müller, J. P., Mertins, K., Zelm, M. (Eds.). Enterprise Interoperability II, Proceedings of the 3rd International Conference on Interoperability for Enterprise Software and Applications (I-ESA 2007), Berlin: Springer. 725–728. Legner C., Lebreton B. (2007) Business Interoperability Research: Present Achievements and Upcoming Challenges. Electronic Markets, 17(3): 176-186.
Improving Interoperability using a UML Profile for Enterprise Modelling Reyes Grangel1, Ricardo Chalmeta1, Cristina Campos1, Sergio Palomero1 1
Grupo de Investigación en Integración y Re-Ingeniería de Sistemas (IRIS), Dep. de Llenguatges i Sistemes Informàtics, Universitat Jaume I, 12071 Castelló, Spain
Abstract. Enterprise Modelling has been successfully used for modelling different enterprise dimensions such as business processes or organisation. However, some problems, like the lack of interoperability, are not solved in this context because the large number of different Enterprise Modelling Languages that exist make it difficult to exchange enterprise models performed by different enterprises. To solve this problem, in this paper we present a Framework that can be used to model enterprise dimensions, at the same time making interoperability between resulting models much easier to achieve. This Framework is based on UML using UML Profiles, and on the existing Enterprise Modelling metamodels proposed to solve interoperability problems. This paper provides a general description of the Framework that was implemented, as well as a detailed explanation of the UML Profile that was developed to represent one of the enterprise dimensions that can be modelled with the Framework, in particular the Organisational Structure of an enterprise. Keywords: Interoperability, Enterprise Modelling, Enterprise Modelling Language, UML, UML Profile, Organisational Structure
1. Introduction One of the main problems in Enterprise Modelling is the huge number of proprietary Enterprise Modelling Languages (EMLs) that exist, since interoperability problems increase among systems that use different EMLs when they want to exchange enterprise models [1-4]. Initiatives such as UEML1 [6-8]
1 Unified Enterprise Modelling Language first developed by the UEML Thematic Network [5] and then worked on by INTEROP NoE [3].
36
R. Grangel, R. Chalmeta, C. Campos and S. Palomero
and POP*2 [9, 10] provide common exchange formats to smooth the exchange of enterprise models in order to solve interoperability problems at Enterprise Modelling level. These two initiatives have been defined with the objective of making it easier to accomplish exchanges among enterprises that used different EMLs. For this reason, they propose common metamodels based on the main EMLs in which several enterprise dimensions, such as 'Process', 'Organisation', 'Product', etc. and the concepts related to each one of them are defined. MDA, on the other hand, is an emerging paradigm defined by the OMG. In this context, a lot of research work is being conducted in relation to PIM (Platform Independent Model) and PSM (Platform Specific Model), but the characterisation of CIM (Computation Independent Model) and the features that an enterprise model must satisfy in order to be considered a CIM and generate appropriate software is still in progress [11]. In fact, there exist several working groups inside the OMG3, which are working on this topic and whose main results (Business Motivation Model (BMM), Business Process Modeling Notation (BPMN), Semantics of Business Vocabulary and Business Rules (SBVR), etc.) highlight the interest of this topic. The objective of this paper is to present a Framework based on the Unified Modeling Language (UML) for modelling enterprises that takes these two contexts into account. In particular, one of the profiles of this Framework, the UML Profile for modelling the Organisational Structure of an enterprise, is detailed. The main reason why this is more than just another Enterprise Modelling Profile, that is different from the existing ones [12, 13] is that it is based on the accepted metamodels performed in UEML and POP*, in which interoperability problems have been solved. These proposals provide metamodels that make it easier to exchange of enterprise models between enterprises that use different EMLs. They do not, however, provide an implementation of these metamodels to be used for engineers to model enterprises directly. The UML Profiles developed inside the Framework presented in this paper are based on these metamodels and they can be used to model enterprises directly. Section 2 describes the main concepts related to UEML and POP* for modelling enterprises, especially organisational dimension, and different approaches that use UML for Enterprise Modelling. In Section 3, the Framework proposed based on UML for Enterprise Modelling is presented. Section 4 shows the detailed UML Profile for modelling Organisational Structure of an enterprise, and Section 5 outlines the conclusions and the main lessons learned for the application of the Framework.
2
Acronym of the different enterprise dimensions: Process, Organisation, Product, and so on (represented by a star), proposed by ATHENA IP [4]. 3 This is the Business Modeling & Integration Domain Task Force whose mission is to develop specifications of integrated models to support management of an enterprise.
Improving Interoperability using a UML Profiles for Enterprise Modelling
37
2. Enterprise Modelling 2.1. Using UEML and POP* In its latest version, UEML contains (1) a construct template, which provides a common structured format for describing modelling constructs; (2) a common ontology, to maintain the classes, properties, states and events used to describe modelling constructs; (3) the meta-metamodel, in which the top part is for managing the relationships between languages, their diagram types and their modelling constructs, the bottom part shows the structure of the common ontology, and the middle part is for breaking down modelling constructs and mapping them onto the common ontology [8, 14]. The UEML approach for describing modelling constructs is sufficiently powerful to support the integrated use of a broad variety of languages and models. However, the resulting theory and tools also need to be empirically validated and evaluated in real case studies [8, 14]. On the other hand, within its specification POP* also includes the POP* metamodel, which describes the set of basic modelling constructs that have been defined and their relationships, as well as some guidelines that describe the management and use of the POP* metamodel. A thorough explanation of the POP* metamodel and its corresponding methodology can be found in [9]. This work includes the description of the POP* metamodel with the dimensions that have been defined so far, i.e. Process, Organisation, Decision and Infrastructure. Organisation dimension expresses the formal and informal organisational structures of an enterprise, as well as the different stakeholders and relationships that form part of this organisation. The metamodel for the Organisation dimension proposes the following concepts with which to model this dimension: Organisation Unit, Organisation Role, Role (General Concept), Enterprise Object (General concepts), and Person. 2.2. Using UML The Unified Modeling Language (UML) has become a standard visual language for object-oriented modelling that has been successfully used for modelling information systems in very different domains [15]. However, UML is a generalpurpose modelling language that can also be useful for modelling other types of systems such as, for example, an enterprise [12, 13]. Other works, such as [16], point out the possibility of using UML as a language for Enterprise Modelling, although how and under which conditions this can be performed are explained in [17]. However, the benefits of model-driven approaches and the new UML2 specification provided by the OMG suggest the need to provide more practical examples for Enterprise Modelling with UML based on these recent works [18], and especially for Enterprise Knowledge Modelling.
38
R. Grangel, R. Chalmeta, C. Campos and S. Palomero
Furthermore, despite the fact that the weakness of the stereotype mechanism is pointed out in [17], the new UML2 specification [15] provides profiles that are more complete than those in version 1.5 [19]. It will therefore be possible to customise UML in a better way [20, 21]. Moreover, taking into account the number of diagrams provided in UML2 and the fact that the previous works use mainly 'Class Diagrams', it would be interesting to clarify exactly which UML2 diagrams are useful at the CIM level and then to specify which part of CIM models must be transformed into PIM models, since according to [22] there must surely be degrees of CIMness.
3. Conceptual Framework for Enterprise Knowledge Modelling The Framework for Enterprise Modelling presented in this paper is part of a bigger project dedicated to the development of Knowledge Management Systems (KMSs). The main results of this project are: (1) the KM-IRIS Methodology for the Implementation of KMSs [23]; and the proposal presented in this paper to model enterprises, the aim of which is to represent Enterprise Knowledge at the CIM level in order to obtain a graphical model called an Enterprise Knowledge Map [24]. Table 1. Proposal for Enterprise Knowledge Modeling Abstraction Level
Metamodel
UML Profile
Model
CIMKnowledge
Knowledge
UML Profile for KM
Knowledge
CIMBusiness
Organisation
UML Profile for GM UML Profile for OSM
Organisation
UML Profile for AM UML Profile for BRM UML Profile for SM
Structure
UML Profile for BM
Behaviour
Diagram Blocks Ontological Knowledge Goals Organisational Structure Analysis Business Rules Product Resource Process Service
In general terms, this proposal is based on MDA and defines a framework for developing conceptual models of KMSs at the CIM level. In other words, it allows enterprise knowledge to be modelled on the CIM level at two levels of abstraction, which are required due to the great complexity of this level (see Table 1.): • CIM-Knowledge: this corresponds to the top level of the model at the CIM level; the enterprise is represented from a holistic point of view, thus
Improving Interoperability using a UML Profiles for Enterprise Modelling
•
39
providing a general vision of the enterprise focused on representing enterprise knowledge that will later be detailed in a local way in successive lower levels. CIM-Business: here, the vision of enterprise knowledge is detailed by means of a representation of its business, according to three types of models, i.e. the Organisational Model, the Structure Model and the Behaviour Model.
The Framework (see Figure 1) also adheres to the following principles: (1) it is focused on Enterprise Modelling, since it takes into account enterprise dimensions and previous works leading to initiatives such as UEML and POP*; and (2) it is a user-oriented modelling framework, since it should be developed at the CIM level by domain experts. A summary of the Framework showing its levels of abstraction, metamodels and profiles, as well as the models and diagrams proposed for each level are shown in Table 1 [24].
Fig. 1. Models and diagrams defined within the Framework
4. Modelling Organisational Structure of an Enterprise The Framework for Enterprise Knowledge Modelling presented in this paper is capable of representing the Organisational Structure of an enterprise by means of different diagrams: • Blocks, Ontological and Knowledge Diagrams: these are able to represent the ontology defined for the human resources and the specific knowledge and instances defined for each category.
40
R. Grangel, R. Chalmeta, C. Campos and S. Palomero
•
Organisational Structure Diagram: this makes it possible to represent the organisation of the human resources in an enterprise, mainly by means of organisational units and the roles played by employees. • Resource Diagram: this makes it possible to model material and human resources. In this latter case, the diagram represents properties such as competencies, skills, knowledge, curriculum, and so on. This section shows an excerpt from the Framework in order to describe how Organisational Structure can be modelled in enterprises. It therefore shows an excerpt from the Organisation Metamodel and the UML Profile for OSM. 4.1. Organisational Structure Metamodel Figure 2 shows an excerpt from the Organisational Structure Metamodel. The constructs needed to represent human resources in an organisation in order to model Organisational Structure are as follows (see Fig. 2). • Enterprise: it represents any kind of organisation. This construct makes it possible to represent both an individual enterprise and an isolated entity (such as an extended or virtual enterprise) made up of different enterprises with distinct legal personalities. The following attributes are defined: - collaboration: it specifies the type of cooperation that enterprises maintain with other organisations in their environment. Its values can be any of those from the enumeration 'EnterpriseCollaborationType': single, extended or virtual. - legalStatus: it specifies the legal form that an enterprise has. - legalName: it indicates the legal name assigned to an enterprise. - cif: it specifies the fiscal identifier of an enterprise. • Unit: it represents each of the logical groups that exist in enterprises to implement their organisation, and may be one of the following types: department, organisational unit, section, and subsection. Furthermore, this construct makes it possible to design tree-shaped hierarchies that describe the organisational structure of enterprises. The following attributes are defined for this class: - type: it specifies the category the unit belongs to and may be one of the categories defined in the enumeration, 'UnitType': department, organisationalUnit, section or subsection. - isLeaf: it indicates whether a unit can no longer be broken down into another level, that is to say, if it is a leaf in the hierarchical tree that makes up organisational units. - connection: it indicates which of the two possible types of connection defined in the enumeration 'UnitConnectionType' (internal or external) exists among specific units in the organisation.
Improving Interoperability using a UML Profiles for Enterprise Modelling
-
41
location: it specifies the physical location of a unit.
Fig 2. An excerpt from the Organisational Structure Metamodel
•
•
• •
JobProfile: it represents a set of tasks that are related and require complementary and specific competences in order to be performed. The job profile defines the tasks and roles that should be performed by whoever has this job profile. The following attributes are defined for this class: - level: it indicates the hierarchical level on which the work position is defined, possible levels may be one from among the following defined by the enumeration 'LevelType': collaborative, strategic, tactic or operative. Employee: it represents the people that carry out a specific work in an enterprise, occupy a work position and have a specific role. The following attributes are defined for this class: - dni: it specifies the unique identifier of each employee. Role: it represents the attitudes and skills that are required for a particular job profile. Task: it represents the individual actions that are responsibility of a single individual and that are assigned to a particular job profile.
42
R. Grangel, R. Chalmeta, C. Campos and S. Palomero
4.2. Implementation of the Proposal From a technological point of view, this Proposal was implemented using the capacity of UML2 to extend a metamodel, that is to say, using a UML2 Profile. The UML2 Profile was defined for Enterprise Knowledge Modelling at the CIM level, following an MDA approach and the principles detailed above, and it was implemented using the IBM Rational Software Modeler [25]. The Profile provides the constructs needed to create the models proposed earlier (see Table 1). The 'UML Profile for OSM' (see Fig. 3) is one of the profiles of this Framework (see Table 1). It allows the organisational structure of an enterprise to be represented, showing the division of work carried out in departments, sections, subsections, etc. as well as the different profiles of jobs existing in enterprises, related employees, roles played by these employees and associated tasks.
Fig. 3. UML Profile for Organisational Structure Modelling
This profile makes it possible to develop the 'Organisational Structure Diagram' (one of the components of the 'Organisation Model') in order to represent the chart diagram of an enterprise. This diagram can include both the organisational units as the job profiles, roles and employees in each one of them. The main stereotypes of the 'UML Profile for OSM' that can be utilised to develop the Organisation Structure Diagram are shown in Table 2.
5. Conclusion The Framework outlined in this paper allows enterprises to be modelled using UML as EML. This Framework was applied in two real cases, an audit enterprise
Improving Interoperability using a UML Profiles for Enterprise Modelling
43
and a foundation, the results of which were used to improve iteratively the metamodels and the profiles presented in this paper. The proposal can be used to model any kind of enterprise, although as explained in the KM-IRIS Methodology [23] the first step is to define which kind of models are suitable bearing in mind the size of the enterprise, its strategic objectives, and so forth. Table 2. Stereotypes and icons that can be used within the 'Organisational Structure Diagram' Stereotype
Elements to model
<<Enterprise>>
Individual or collaborative enterprise
<>
Any of the organisational units of an enterprise, i.e. departments, organisational units, sections, subsections, etc.
<<JobProfile>>
Job profiles
<<Employee>>
Employees in the enterprise
<>
Employees' roles
<>
Tasks in a particular work place
Icon
<>
The main lessons learned is the difficulty involved in explaining the meaning of each concept proposed in the Framework to final users, since, in a similar way to UML, it is necessary to use diagrams to explain what each concept is and how it can be used to represent the particular case of an enterprise. For this reason, future work is centred on providing a number of templates that can guide the process of modelling and, on the other hand, on validating and improving the Framework with more real cases from different sectors and types of enterprises.
6. Acknowledgements This work was funded by DPI2006-14708 and the EC within the 6th FP, INTEROP NoE (IST-2003-508011 [3]).
44
R. Grangel, R. Chalmeta, C. Campos and S. Palomero
7. References [1] [2]
[3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19]
Chen, D., Doumeingts, G.: European initiatives to develop interoperability of enterprise applications–basic concepts, framework and roadmap. Annual Reviews in Control 27 (2003) 153–162 Doumeingts, G., Chen, D.: Interoperability development for enterprise applications and software. In Cunningham, P., Cunningham, M., Fatelnig, P., eds.: Building the Knowledge Economy: Issues, Applications, Case Studies. eBusiness, IOS Press Amsterdam (2003) INTEROP: Interoperability Research for Networked Enterprises Applications and Software NoE (IST-2003-508011). http://www.interop-noe.org (2010) ATHENA: Advanced Technologies for interoperability of Heterogeneous Enterprise Networks and their Applications IP (IST-2001-507849). http://www.athena-ip.org (2010) UEML: Unified Enterprise Modelling Language Themantic Network (IST-200134229). http://www.ueml.org (2010) UEML: Unified Enterprise Modelling Language Project (IST-2001-34229). http://www.ueml.org (2004) Deliverable 1.1. Berio, G., Opdahl, A., Anaya, V., Dassisti, M.: Deliverable DEM 1: UEML 2.1. Technical report, INTEROP-DEM (2005) Opdahl, A., Berio, G.: A Roadmap for UEML. In: Enterprise Interoperability. Springer-Verlag (2007) Ohren, O.P.: Deliverable DA1.3.1. Report on Methodology description and guidelines definition. Technical report, ATHENA Project (IST-2003-2004) (2005) Grangel, R., Chalmeta, R., Schuster, S., Peña, I.: Exchange of Business Process Models using the POP* Meta-model. In: Int. Workshop ENEI’2005. Vol. 3812/2005 of LNCS, Springer-Verlag (2005) Grangel, R., Chalmeta, R., Campos, C.: Enterprise Modelling, an overview focused on software generation. In Panetto, H., ed.: I-ESA Workshops of the INTEROP-ESA Int. Conf. EI2N, WSI, ISIDI and IEHENA 2005, Hermes Science Publishing (2005) Eriksson, H., Penker, M.: Business Modeling with UML: Business Patterns at Work. J. Wiley (2000) Marshall, C.: Enterprise Modeling with UML. Designing Successful Software Through Business Analysis. Addison Wesley (2000) Opdahl, A.: The UEML Approach to Modelling Construct Description. In: Enterprise Interoperability. Springer-Verlag (2007) OMG: UML 2.1.2 Superstructure. Object Management Group. version 2.1.2 formal/2007-11-04 edn. (2007) Panetto, H.: UML Semantics Representation of Enterprise Modelling Constructs. In: ICEIMT. (2002) 381–387 Berio, G., Petit, M.: Enterprise Modelling and the UML: (sometimes) a conflict without a case. In: Proc. of 10th ISPE International Conf. on Concurrent Engineering: Research and applications. (2003) 26–30 Grangel, R., Bourey, J.P., Chalmeta, R., Bigand, M.: UML for Enterprise Modelling: a Model-Driven Approach. In: I-ESA’06. (2006) OMG: OMG Unified Modeling Language Specification, version 1.5. Object Management Group. formal/03-03-01 edn. (2003)
Improving Interoperability using a UML Profiles for Enterprise Modelling
45
[20] Fuentes, L., Vallecillo, A., Troya, J.: Using UML Profiles for Documenting WebBased Application Frameworks. Annals of Software Engineering 13 (2002) 249–264 [21] Noran, O.: UML vs. IDEF: An Ontology-Oriented Comparative Study in View of Business Modelling. In: ICEIS (3). (2004) 674–682 [22] Berrisford, G.: Why IT veterans are sceptical about MDA. In: Second European Workshop on Model Driven Architecture (MDA) with an emphasis on Methodologies and Transformations, Kent, Computing Laboratory, University of Kent (2004) 125– 135 http://www.cs.kent.ac.uk/projects/kmf/mdaworkshop/submissions/Berrisford.pdf. [23] Chalmeta, R., Grangel, R.: Methodology for the Implementation of Knowledge Management Systems. Journal of the American Society for Information Science and Technology 59 (2008) 1–14 John Wiley & Sons. [24] Grangel, R., Chalmeta, R., Campos, C.: A Modelling Framework for Sharing Knowledge. In: Int. Conf. KES 2007. Vol 4693/2007 of LNAI, Springer-Verlag (2007) [25] IBM: IBM Rational Software Modeler Development Platform 6.0.1. http://www306.ibm.com/software/rational/ (2010)
Towards Test Framework for Efficient and Reusable Global e-Business Test Beds Nenad Ivezic1, Jungyub Woo1 and Hyunbo Cho2 1 2
National Institute of Standards and Technology, 100 Bureau Drive, Gaithersburg, MD 20899, USA Pohang University of Science and Technology, San 31, Hyoja, Pohang 790-784, Korea
Abstract. We introduce a novel Agile Test Framework (ATF) for eBusiness systems interoperability and conformance testing. Largely, existing test frameworks have been designed to only consider a limited collection of specific test requirements. This makes it difficult to apply these frameworks to other similar standards specifications and to support cooperative work in building distributed global test systems. ATF addresses the core issues found in these traditional testing frameworks to alleviate the resulting inefficiencies and lack-of-reuse problems that arise in the development of eBusiness test beds. Keywords: testing, eBusiness, interoperability, conformance, test framework, test bed, reusability
1. Introduction There exists an increasing need to build efficiently test beds in support of interoperable e-Business applications. For example, a recent international activity was completed under auspicies of the European Committee for Standardization (CEN) to perform a feasibility analysis of the Global Interoperability Test Bed (GITB) for eBusiness systems [1]. The goal of this activity was to establish a foundation for development of a common test framework (i.e., the GITB) for efficient development of global, distributed test beds for eBusiness. Specifically, the activity envisions and recommends development of a shared architecture for the test framework. The objective of this paper is to contribute to a basis for architectural development of the test frameworks that enable efficient building and re-use of test beds for interoperable eBusiness applications. Here, we introduce the Agile Test Framework (ATF) that represents a refinement of our lessons learned of developing test beds for e-Business systems over many years.
48
N. Ivezic, J. Woo, and H. Cho
The rest of the paper is organized as follows: first, we summarize findings of the feasibility analysis of the Global Interoperability Test Bed (GITB) for eBusiness systems. Then, we identify the issues that disqualify certain test frameworks from becoming a solid basis for the GITB. Next, we present design decisions that resolve the previous issues and describe the conceptual architecture for the proposed ATF framework. Finally, we summarize the findings in the paper.
2. Recommendations for the Global Interoperability Test Bed The following is a summary of the GITB project recommendations that directly impact the test framework architectural concerns [1]: • •
•
•
Promote the development of an integrated test framework which (1) does not hard-code a specific standard at any layer and (2) is capable of handling testing activities at all layers of the interoperability stack. Support the implementation of the test framework in a decentralized approach, as a network of multiple test beds and test services. The essential foundations are (1) a standardized testing framework (covering test execution and test case model), (2) a coherent architecture, (3) a common platform, and (4) access method. Also, the functional requirements should be implemented as plug-and-play components to leverage existing standards. In addition, emphasis needs to be given to non-functional capabilities, such as modularity and extensibility. Ensure that industry consortia and standard development organizations (SDOs) address the needs for testing as part of the standardization effort and to enable them to use the test framework. Specifically, in order to allow testing, standards specifications need to (1) complement narrative or semi-formal specifications by formal representations wherever possible; (2) define conformance criteria for compliance with the standard; and (3) comprise implementation guidelines and outline the testing approach and test cases. Conceive the GITB architecture as a set of test services, provided by several test service providers, which may be plugged in test infrastructure based on common interfaces. Focus on modularity and reusability of testing services and components. Provide for test services categorization in support of development of standardized interfaces.
Clearly, a foremost concern is that the test framework architecture promotes efficient development and reusability of testing facilities across different domains and different standards.
3. Issues with Test Frameworks Most existing test frameworks are limited in terms of reuse. Even new frameworks do not aim to maximize reuse of testing facilities and materials, although at least
Towards Test Framework for Efficient and Reusable Global e-Business Test Beds
49
one recent test framework has invested significant effort to address dynamic, configurable, and fully automated execution of conformance and interoperability test scenarios [2]. Most test frameworks are proposed with the purpose of meeting the requirements of testing for only a specific standard and a specific Test User’s usage. Therefore, their scope is generally narrow, and the provided functionalities cannot be applied easily to similar testing requirements in which, for example, a related standard specification is the subject of testing. For instance, the IIC test framework focuses on the ebMS (ebXML Messaging Specification) [3], the RossettaNet self-test toolkit only deals with the conformance test for RossettaNet PIP systems [4], and the WS-I tool only checks the data integrity of Web Service request/response messages [5]. That is, to test conformance with respect to each standard specification, development of different test frameworks was required such that the facile adaptation of the framework to related standard specifications was forbidden. For example, the IIC framework requires significant changes before it is applicable to related messaging standards, such as WS messaging. Even test frameworks, such as TTCN [6] and eTSM [7], that have been developed to overcome such a narrow scope of application, cannot effectively deal with new similar test requirements, because the test frameworks were not designed with sufficient modularity and extensibility.
Fig. 1. Activity Diagram for Standards-based Testing using Existing Test Frameworks
Figure 1. conceptually describes the typical usage of existing test frameworks – from test requirements to test bed execution. Once the Test User introduces their specific requirements for the intended usage of the standard specification of interest (e.g., by providing a specific business process or pattern of usage), the Test Case Developer composes test cases based on the grammar and structure of test case scripts designed for that particular test framework. At this time, the composed
50
N. Ivezic, J. Woo, and H. Cho
test case is machine-readable and tightly bound to the specific test requirements and specific test platform. By this we mean that the current test frameworks are designed for specific test requirements, specific user environments, and specific implemented testing tools – a specific test platform. The figure indicates this situation by situating the ‘Compose Executable Test Case’ and ‘Implement Test Bed’ activities within the Implementation Phase, supported by the Platform Specific Model (PSM). On the other hand, as shown on the right side of Figure 1, the Test Bed Architect extracts the test bed functional requirements from the Test User’s test requirements to implement a specific test bed based on these functional requirements. At the Execution Phase, the Specific Test Bed uses the Executable Test Cases and verifies the system under test. In summary, existing test frameworks have been designed to only consider a limited collection of specific test requirements, which makes it difficult to apply these frameworks to other standards specifications (regardless of similarity) or to support cooperative work in building distributed global test systems because of the following problems: •
Problem I. Test case dependency on the test bed and test case implementation decisions: The existing frameworks promote test case designs that depend on specific test bed design decisions. For example, a IIC test case cannot represent SUT activities during a test because the IIC test beds, which follow the IIC test framework specification, do not utilize information from the SUT activities (i.e., the test beds cannot control the SUT). This obviously prevents reuse of the test cases in situations in which new test beds are developed according to a common test framework but with different implementation decisions. In the IIC test framework case, new test beds, in which the test bed role changes (say, from a customer to a supplier), would not be able to reuse the previously developed test cases. Also, most test case designs are developed with consideration for specific test implementation requirements, such as a standard specification. For example WS-I tool’s test case cannot represent non-XML content as a test material, because it is designed only for XML-based web service testing. Therefore, the test case design does not support reusability, because application of the existing test case designs to other standards is often not feasible. Obviously, these two dependencies make test case development a time-consuming and costly process, because Test Case Developers are required to simultaneously consider both constraint types when developing test cases;
•
Problem II. Low configurability of test beds: Most test bed designs only consider a specific testing purpose and take into account specific test bed design decisions. It is, therefore, difficult to adopt one test bed to another, similar, testing situation. Such test beds cannot be re-configured and do not allow new components to be introduced in a pluggable manner to address new functional requirements; and
Towards Test Framework for Efficient and Reusable Global e-Business Test Beds
•
51
Problem III. Low modularity and extensibility of test cases: Most test cases contain both procedure and verification instructions for the data. However, the existing test framework designs do not treat the two types of information separately. Consequently, it is difficult to extract verification data from a test case in order to reuse a specific part of the test case in a related, similar, testing situation.
4. A Service Oriented Architecture for Agile Test Framework 4.1. Overall Approach Our purpose is to resolve the problems identified with the existing test frameworks by introducing new design decisions within a proposed test framework. Most existing test cases depend on both the specific test case implementation requirements and the test bed implementation (as described in Problem I). To resolve this problem, we remove the dependency of the test cases by introducing a two-layer test case design consisting of abstract and executable test case definitions. •
ATF_Design Decision I: Two-level test case design. The ATF test case structure consists of an abstract test case and an executable test case. The abstract test case is a human-readable, high level description of a test case. To enhance the reusability of the test case, an abstract test case does not contain specific implementation-level information. On the other hand, an executable test case is a machine-readable, low level description of a test case. The executable test case can be obtained by transformation from an abstract test case, when provided additional specific testing environment information (e.g., messaging protocol specification, a specific verification component, and a communication channel between the SUT and test bed). The existing test frameworks promote test case designs that are executable test cases. The addition of abstract test case descriptions is expected to have three benefits: 1) the abstract test case can be developed early in the design process without requirements for the test bed systems details, providing a clear specification of intent for the test case; 2) the abstract test case can be easily reused when similar test requirements arise, because it has no dependency on a specific test bed implementation; and 3) the abstract test case helps the testing user to understand the executable test case and its procedure and rules. That is, the abstract test case provides a kind of three-way bridge between the Standard Developer, who provides test requirements, the Testing User who verifies the system under test, and the Test Case Developer, who interprets the requirements to create the actual test case. Most existing test bed implementations cannot be re-configured to easily accommodate varying and dynamic functional requirements (as captured in Problem II). This low re-configurability problem makes a test bed difficult to reuse and adapt for new but related functional requirements. To resolve this
52
N. Ivezic, J. Woo, and H. Cho
problem, we propose the use of pluggable test components and infrastructure designs for the test bed implementation. •
ATF_Design Decision II: Pluggable test components and infrastructure designs. The ATF test bed execution model will consist of a test infrastructure with pluggable test components. The test infrastructure will allow assembly of the test components into the implementation of a desired testing service. The test infrastructure is independent of any specific standard and/or Test User’s environment. That is, it may be used for any type of testing without modification. In contrast, pluggable test components are designed and implemented by a test service provider to enable a specific function required for a specific standard and/or Test User’s environment. Normally, the test infrastructure would not provide the functions of the pluggable test component. • ATF_Design Decision III: Event-driven Test Execution design. In an ATF test bed, the pluggable test components are loosely coupled to the test infrastructure. Because it is impossible for the test infrastructure to control a potentially very large set of arbitrary pluggable test components, ATF relies on a generic transaction handler, instead of allowing direct interfacing between the test components. When a component attempts to interact with another component, it sends data to an event board instead of the target component. The event board stores the various types of interaction data as events so that every component can inquire and retrieve a specific event. All of the activities of the pluggable components and the test infrastructure are coordinated via events. When a Service Provider designs a pluggable test component, the design is registered with the Test Service Model Repository to be discovered and reused in similar testing situations. The pluggable test component is automatically deployed (configured) into the test infrastructure prior to a test execution. Introduction of the pluggable test component design anticipates three benefits: 1) the test infrastructure may be consistently reused for many types of testing, 2) the pluggable test components may be conditionally reused for the same testing requirements, and 3) automatic configuration makes the test bed more extensible and reusable. Most existing test cases are designed without separating the procedural definitions and verification rules (as captured in Problem III). This makes the test case virtually impossible to reuse and difficult to manage for large scale test suites (i.e., sets of test cases). To resolve this problem, we introduce two design decisions: •
ATF_Design Decision IV: Modular test case design. The abstract test case will consist of two design modules: assertion and procedure modules. Such a design yields an abstract test case which is not only easier to read but also easier to reuse, because the Test Bed Manager may reuse each module separately when the test case is adapted for different test requirements. In the executable test case, procedure and assertion content (scripts) will be separated for reuse in new executable test cases.
Towards Test Framework for Efficient and Reusable Global e-Business Test Beds
53
•
ATF_Design Decision V: Event-centric test case design. Every type of event - from low-level protocol signals (e.g. Acknowledgements) to business document receipts - may be captured by the event board and wrapped into a standard event envelope. Virtually all testing events are captured, stored, and may be used to trigger an arbitrary testing activity, such as a data extraction procedure or verification action. Because every assertion or procedure module in the test case contains triggering conditions, each module can be independently introduced and managed. By introducing a modular and event-centric design for test cases, we expect two benefits: 1) each module, either procedure or assertion, may be independently reused by another test case; and 2) because the test case module is not affected by other changes in the module, a Test Case Developer may easily manage large scale test suites.
Fig. 2. Procedure Architecture of the Agile Test Framework
4.2. Service Oriented Architecture for Agile Test Framework This section provides a high-level view of the ATF architecture and supported processes, as illustrated in Figure 2. Because the ATF architecture is designed according to the ATF design decisions discussed previously, Figure 2 illustrates the major differences between ATF and existing test frameworks, shown in Figure 1. First, the design phase (corresponding to Platform Independent Model (PIM)) is positioned between the conceptual and implementation phases. Actions in this phase are abstract and independent of a specific test bed implementation. The
54
N. Ivezic, J. Woo, and H. Cho
previous Test Bed Architect role now is broken into the three new roles: Test Service Provider, Test Bed Manager, and Test Framework Provider. The new roles and their activities reflect the drive towards greater modularity and reusability. Each test case has separate modules for verification rules and procedural data. The following are descriptions of the key processes supported by the ATF architecture: •
•
•
•
•
Analyze Test Requirements: The Test Case Developer investigates the requirements given by a standard specification and a specification for intended usage of the standard. He/she determines the functions that need to verify the identified Test User’s SUT. Compose Abstract Test Cases: An abstract test case consists of usage and assertion scripts. From the given test requirements, a collection of abstract test cases is developed (1) to represent the required scenarios as usage scripts that extract test items from the SUT, and (2) to provide predicates (i.e., true–false statements) as assertion scripts to determine whether the test item is true or false. The generated abstract test case is not machinereadable because it is generated without concern for a specific harness script. That is, an abstract test case does not describe a concrete test environment (e.g., message protocol) or specific configuration (i.e., included test components) for a specific test bed. Therefore, an abstract test case is independent of a specific test bed implementation and is a kind of meta-model for an executable test case. Compose Executable Test Cases: An executable test case consists of verification and procedure scripts. Such an executable test case is generated from a corresponding abstract test case after considering a specific test harness specification (or script). In other words, after the test environment and configuration information regarding the partner(s) and target SUT(s), pluggable test components to be used for the testing, protocol and schema to be used for business documents, etc., are decided and specified within the test harness script by the Test Bed Manager, the Test Case Developer may generate a machine-readable executable test case from an abstract test case. This test environment and configuration information is encoded as a harness script by the Test Bed Manager. The generated executable test case is registered into the test case repository. Analyze Functional Non-stationary Requirements: The Test Bed Manager investigates functional non-stationary requirements based on the test requirements. A non-stationary requirement is a specific test service requirement for a specific testing situation. That is, the test service is required for a testing scenario at hand but it may not be used in other testing situations without additional adaptation. Design and Register Pluggable Test Components: The pluggable test component provides a specific test service. A Test Service Provider designs the pluggable test component according to the standard specification and the interface specification for the pluggable test components. Once the pluggable test component is designed, it should be registered in a public
Towards Test Framework for Efficient and Reusable Global e-Business Test Beds
•
•
•
•
55
service registry. At that time, the Test Service Provider registers the information, such as technical capabilities, service interface, and index of service categorization, which are described in Section 5.4. Search and Select Pluggable Test Components: The Test Bed Manager searches for the relevant pluggable test components that are needed for the specific test bed. The Test Bed Manager decides the optimal set of pluggable test components among the alternative components. Generate Harness Script: The Test Bed Manager composes the harness script, which contains the test environment and configuration information describing the partner(s) and target SUT(s), pluggable test components to be used for the testing, the protocol and schema to be used for business documents, and other information necessary to assemble the required test bed. Implement Pluggable Test Component: The Test Service Provider implements and customizes a pluggable test component based on the pluggable test component design and specific interface requirements described in the harness script provided by the Test Bed Manager. Assemble Test Bed and Execute Test Case: A test bed is automatically configured on the basis of information contained in the harness script. That is, a test bed is assembled from the test infrastructure and the selected loosely coupled pluggable test components. Finally the test bed interprets and executes the executable test case to verify the system under test.
5. Conclusions In this paper, we have presented a novel Agile Test Framework (ATF) for B2B testing, which addresses the core issues found in traditional testing frameworks to alleviate the resulting inefficiencies and lack-of-reuse problems that arise in the development of B2B test beds. First, traditional test case designs rely on specific test bed and test case implementation decisions. In the ATF architecture, this issue is addressed by introducing the concept of an abstract test case, which insulates the test case specifications from the implementation details and from the specific testing platform decisions. The executable test cases are obtained by way of a transformation, only when the specific test bed configuration is specified. Second, traditional test execution models rely on specific testing requirements and do not consider the reuse of testing modules in similar situations. In the ATF architecture, the issue is addressed by introducing the concepts of test infrastructure, the pluggable test components, and event-driven execution. The test infrastructure contains readily reusable core functionalities that allow assembly of the test components into novel implementations of desired testing services. By way of event-driven execution, ATF provides a generic transaction handler, an event board, which coordinates and facilitates communication between the infrastructure and pluggable components. Third, traditional test case designs do not recognize and separate procedural and verification aspects of the test case, which makes test cases impossible to
56
N. Ivezic, J. Woo, and H. Cho
reuse. In the ATF architecture, the issue is addressed by introducing modular and event-centric test case design. The modular design separates two types of information: assertions and procedural information. The event-centric design allows assertion and procedure modules in the test case to contain triggering conditions, which allows each module to be independently managed and reused. Following these ATF architectural decisions, we are presently completing the necessary details for the test case design and execution model. The detailed design will be followed by a comparison of the proposed architecture with other existing test framework architectures. Our goal is to assure that the global, distributed eBusiness test beds are efficiently developed by reusing existing testing services while successfully addressing complex e-Business testing situations.
6. Disclaimer Certain commercial software products are identified in this paper. These products were used only for demonstration purposes. This use does not imply approval or endorsement by NIST, nor does it imply these products are necessarily the best available for the purpose.
7. References [1] [2] [3] [4] [5] [6] [7]
GITB (Global eBusiness Interoperability Test Bed Methodologies), on line at www.ebusiness-testbed.eu, accessed December 2009. TestBATN – Testing Business, Application, Transport, and Network Layers Web Site, on line at www.srdc.com.tr/testBATN, accessed December 2009. IIC ("ebXML IIC Test Framework Version 1.0." OASIS), on line at http://www.oasisopen.org/committees/download.php/1990/ebXML-TestFramework-10.zip, accessed December 2009. RosettaNet (RosettaNet Ready Self-Test Kit (STK) User’s Guide Release Version 2.0.7). RosettaNet, 2004. WS-I tool site, on line at http://ws-i.org, accessed December 2009. TTCN-3 site, on line at http://www.ttcn-3.org, accessed December 2009. TaMIE Site, on line at http://www.oasis-open.org/committees/tamie, accessed December 2009.
Unified Reversible Life Cycle for Future Interoperable Enterprise Distributed Information Systems Zhiying Tu1, Gregory Zacharewicz1 , David Chen1 1
IMS-LAPS / GRAI, Université de Bordeaux – CNRS, 351, Cours de laLibération,33405, TALENCE cedex, France
Abstract. This paper aims at improving the re-implementation of existing information systems when they are called to be involved in a system of systems, i.e. a federation of enterprise information systems that interoperate. The idea is reusing the local experiences coming from the development of the original information system with the process of Model Discovery and Ontological approach. We give first, a review of ongoing researches on Enterprise Interoperability. The MDA can help to transform concepts and models from the conceptual level to the implementation. The HLA standard, initially designed for military M&S purpose, can be transposed for enterprise interoperability at the implementation level, reusing the years of experiences in distributed systems. From these postulates, we propose a MDA/HLA lifecycle to implement distributed enterprise models from the conceptual level of federated enterprise interoperability approach. In addition to this classical development, we propose a model reversal methodology to help re-implement the legacy information system, in order to achieve the interoperability with other systems. Keywords: Interoperabilitty, HLA, MDA, FEDEP, Information System
1. Introduction In the globalised economic context, the competitiveness of an enterprise depends not only on its internal productivity and performance, but also on its ability to collaborate with others. This necessity led to the development of a new concept called interoperability that allows improving collaborations between enterprises. No doubt, in such context where more and more networked enterprises are developed; enterprise interoperability is seen as a more suitable solution to total enterprise integration. Since the beginning of 2000, several European research projects have been launched to develop enterprise interoperability (IDEAS, ATHENA, INTEROP). Three main research themes or domains that address interoperability issues were identified, namely: (1) Enterprise modeling (EM) dealing with the representation
58
Z. Tu, G. Zacharewicz and D. Chen
of the inter-networked organization to establish interoperability requirements; (2) Architecture & Platform (A&P) defining the implementation solution to achieve interoperability; (3) Ontologies (ON) addressing the semantics necessary to assure interoperability. This paper intends to propose an improvement of the re-implementation of existing information systems when they are called to be involved in a system of systems. Compare to the traditional IS and Simulation development process, we involve the bottom-up process of Model Discovery and Ontological approach into our framework. In the framework, first, we align MDA and HLA to propose a lifecycle to implement distributed enterprise models from the conceptual level of federated enterprise interoperability approach. Besides that, a model reversal methodology is integrated with the MDA/HLA development lifecycle to assist reengineer the legacy information system, in order to achieve interoperability with other systems. The paper is structured as follows. We start out with a survey of related work in the area of HLA, MDA and their harmonization, as well as in the area of reengineering to model-driven architectures (section 2). Then, we describe our motivation of this work (section 3). After that, we explain two main parts of our methodology, alignment of MDA and HLA FEDEP (section 4) and Model Reversal (section 5).
2. IS and Simulation Development Life Cycle: State-of-the-Art 2.1. HLA The High Level Architecture (HLA) is a software architecture specification that defines how to create a global software execution composed of distributed simulations and software applications. This standard was originally introduced by the Defense Modeling and Simulation Office (DMSO) of the US Department Of Defense (DOD). The original goal was reuse and interoperability of military applications, simulations and sensors. In HLA, every participating application is called federate. A federate interacts with other federates within a HLA federation, which is in fact a group of federates. The HLA set of definitions brought about the creation of the standard 1.3 in 1996, which evolved to HLA 1516 in 2000 [1]. The interface specification of HLA describes how to communicate within the federation through the implementation of HLA specification: the Run Time Infrastructure (RTI). Federates interact using services proposed by the RTI. They can notably “Publish” to inform about an intention to send information to the federation and “Subscribe” to reflect some information created and updated by other federates. The information exchanged in HLA is represented in the form of classical object class oriented programming. The two kinds of object exchanged in HLA are Object Class and Interaction Class. Object class contains object-oriented data shared in the federation that persists during the run time; Interaction class data are just sent and
Unified Reversible Life Cycle
59
received information between federates. These objects are implemented within XML format. More details on RTI services and information distributed in HLA are presented in [1]. The FEDEP (Federation Development and Execution Process) describes a highlevel framework for the development and execution of HLA federation. FEDEP uses the seven-step process to guide the spiral development of the simulation system through phases of requirements, conceptual modelling, design, software development, integration, and execution [2]. 2.2. MDA The first methodology studied is Model Driven Architecture (MDA). This methodology defined and adopted by the Object Management Group (OMG) in 2001, (updated in [3]) is designed to promote the use of models and their transformations to consider and implement different systems. It is based on an architecture defining four levels, which goes from general considerations to specific ones. •
• • •
CIM Level (Computation Independent Model): focusing on the whole system and its environment. It is also named « domain model », it describes all work field models (functional, organisational, decisional, process…) of the system with an independent vision from implementation. PIM Level (Platform Independent Model): modelling the sub-set of the system that will be implemented. PSM Level (Platform Specific Model): that takes into account the specificities related to the development platform. Coding Level: The last level consists in coding enterprises applications (ESA: Enterprise Software Application).
To complete this description, a Platform Description Model used for the transformation between PIM level and PSM level is added to these four kinds of models corresponding to four abstraction levels. 2.3. MDA/HLA Harmonization In [4], Andreas Tolk mentions that while the HLA can help the MDA to improve in its principles concerning distributed simulation systems, the MDA can help the HLA implementers to improve their products based on the experiences of the OMG partners and the related software industry. Meanwhile, [4] proposes to consider five aspects for merge HLA and MDA together: Domain Facilities, Pervasive Services, RTI as Middleware, Federation Development Tools, and Data Engineering. A solution of applying MDA to HLA is proposed in [5]. In this methodology, the Component-based development (CBD) is underlined. The design goals and philosophy of CBD also share many similarities with the goals of HLA federate development, including the promotion of reuse and interoperability. However, HLA currently has no standardized development approach to CBD, known as a
60
Z. Tu, G. Zacharewicz and D. Chen
component model, analogous to the CORBA Component Model (CCM) or the Enterprise Java Bean (EJB) container. As a result, there is no commonality in design and implementation between federates, nor any formal way of separating and reusing the behavioural aspects of an HLA component. This results in an increase in development and maintenance costs, as well as impacting on the potential for reuse outside of the FOM for which the federate was built. As the result, they introduce SCM (simulation component model) into HLA (fig.1.). SCM is one potential candidate for the definition of a standardized model for component-based simulation development. This architecture employs a component model based on the OMG’s CCM, and describes how the separation of integration logic and simulation behaviour can be achieved for an HLA federate. This SCM development model also provides a commonality of design between federates, allowing them to access both HLA and extended CBD services (such as data transformation services between federates and the FOM) in a consistent manner.
Fig. 1. Simulation component model
2.4. MDA/FEDEP As mentioned in [6], FEDEP and MDA are successful within their particular community. FEDEP and MDA are separate, but alignable development life cycle. Each follows basic systems engineering process through analysis is done in the following areas: • • • •
Definition of requirements Definition of attributes and behaviors through a functional analysis of the requirements Expression of requirements, functions and analysis in narrative and graphical form Design of the ‘product’
Unified Reversible Life Cycle
61
Based on the FEDEP MDA alignment shown in fig. 2, [6] also proposes a development lifecycle as illustrated in fig. 3, which surrounds the testing phase, in order to implement the VV&A.
Fig. 2. FEDEP MDA alignment
Fig. 3. FEDEP MDA alignment based lifecycle
2.5. MDA-Based Reverse Engineering A framework to reverse engineering MDA models from object oriented code is presented in [7]. This framework is based on the integration of compiler techniques, metamodeling and formal specification and it also distinguishes three different abstraction levels linked to models, metamodels and formal specifications, as fig. 4 shows. In this framework, the model transformations are based on classical compiler construction techniques at model level. At the metamodel level, MOF metamodels are used to describe the transformations from model level. MOF metamodels describe families of ISMs, PSMs and PIMs. Every ISM, PSM and PIM conforms to a MOF metamodel. Metamodel transformations are specified as OCL contracts
62
Z. Tu, G. Zacharewicz and D. Chen
between a source metamodel and a target metamodel. MOF metamodels “control” the consistency of these transformations. The level of formal specification includes specifications of MOF metamodels and metamodel transformations in the metamodeling language NEREUS that can be used to connect them with different formal and programming languages The transformations are based on static and dynamic analysis at model level [7]. •
•
Static analysis extracts static information that describes the software structure reflected in the software documentation (e.g., the text of the source code). Static information can be extracted by using techniques and tools based on compiler techniques such as parsing and data flow algorithms. Dynamic analysis extracts dynamic analysis information, which describes the structure of the run-behavioral, by using debuggers, event recorders and general tracer tools. Dynamic analysis is based on an execution model including the following components: a set of objects, a set of attributes for each object, a location and value of an object type for each object, and a set of messages. Additionally, types such as Integer, String, Real and Boolean are available for describing types of attributes and parameters of methods or constructors.
Fig. 4. MDA-based reverse engineering framework
3. Studied Context A multiple agent/HLA enterprise interoperability methodology is proposed in [9]. It mentions several enterprises who all participate in a cooperative project, and they need to exchange various information any time, so the framework (fig. 5) defined in the methodology provides a platform based on HLA, where each enterprise plays as a federate and connect to each other.
Unified Reversible Life Cycle
63
Fig. 5. Interoperable System of Information-Systems
However, most of the enterprises will have their own IT system, and sometimes the cooperation among those companies won’t last permanently, some of them could join this group for a very short period time and then quit. Consequently it seems not adequat and luxurious to launch a totally new IT project for this short time cooperation. As the result, how to build the federate for each enterprise merits consideration. Refering to the existing methodologies mentioned in previous sections, we propose a new approach, as the fig. 6 shows, to solve this problem. This methodology will involve MDA&HLA FEDEP alignment in order to use both of their advantages to realize proper component reuse and rapid development. Besides that, in order to achieve a rapid federate development according to the legacy IT system, the model reverse engineering is integrated with this alignment.
4. Alignment of MDA and HLA FEDEP In this section, we propose a new development lifecycle to reconstruct HLA FEDEP and MDA, and generate a new five steps development framework (as shown in fig. 6). This new methodology aims to adopt the strong points from both HLA FEDEP and MDA while overcoming their weak points, then, to achieve proper component reuse and rapid development. Phase 1: Domain Requirment Definition The main task of this phase is to collect clear and enough requirements from customer in order to define the objective of the system, to describe the environment of the system, the senario of the system. At the same time, all these definition and description need to be reasonable, understandable for all the stakeholder. CIM of MDA has more similar task with Define Federation Objectives, Develop Federation scenario together in HLA FEDEP. As the result, we align them in this phase, to convert the user requirement, which is more textual based, into more visual model, such as UML use case to derive the federation requirement, etc.
64
Z. Tu, G. Zacharewicz and D. Chen
Fig. 6. IS and Simulation Devellopment Life Cycle
Phase 2: Domain Scenario Systematization The main task of this phase is to refine the domain scenario and business process defined in the first phase, to identify and describe the entities involved in the scenario and business process. And then, to define the relationships among entities and behaviors, events for each entity, etc. This phase integrates PIM in MDA, which describes the operation of system but doesn’t address the detail platform information yet, as well as steps of Perform Conceptual Analysis, Develop Federation Requirements and Select Federates in HLA FEDEP, which also define and select general participators of the federation, then describe their relationship, behaviours and event in general. Phase 3: System Model Specialization In this phase, according to the technique chosen and platform selected, the system needs to be refined, for instance, to refine federation and federate structure, to allocate functions and attributes, etc. Detailed design will carry out at this time. This phase integrates the following parts in MDA and FEDEP. PSM in MDA, which is in the form of software and hardware manuals or even in an architect’s head, will be based on detailed platform models, for example, models expressed in UML and OCL, or UML, and stored in a MOF compliant repository. The Prepare federation design, Prepare plan, Develop FOM, and Establish federation agreement in FEDEP will produce federate responsibilities, federation architecture, supporting tools, integration plan, VV&A plan, FOM, FED/FDD and time management, date management, distribution agreements, etc. Phase 4: System Implementation This phase’s task is to transfer the specific system model into code, to create the executable federation and runable federate.
Unified Reversible Life Cycle
65
At this level, MDA has various transformation techniques from model to code. In the FEDEP, Implement Federate designs will provide modified and/or new federates and supporting database. Implement Federation Infrastructure will provide implemented federation infrastructure and modified RTI initialization data. Plan Execution and Integrate Federation will provide execution environment description and integrated federation. Phase 5: Test Throughout the previous steps of the MDA and HLA FEDEP alignment process, testing is essential to ensure fidelity of the models. Testing phase includes the Test Federation, Execute Federation and Prepare Outputs, and Analyze Data and Evaluate Results in HLA FEDEP. Meanwhile, it will also refer to the outputs from the previos steps, such as the original user requirment in the first step, and federation test criteria from second phase.
5. Model Reversal This section describes a brand-new process of model reverse engineering with different senarios constraints (see fig. 6). The reverse process will re-characterize the legacy system in order to capitalize on the information and functions of the existing system, and make it easy for reusing in a new HLA compliant system. This methodology will assite to HLA FEDEP / MDA alignment mentioned in previous section, to fully achieve rapid development of federation and/or federate based on the legacy IT systems. We distiguish two kinds of reversal scenarios as following. 1. First, when an enterprise intents to start exchanging information in a new cooperative project with other enterprises. In that case, the HLA federation has not been created yet, so we propose to reverse the code of the legacy information systems to the first definition phase (domain requirment definition). Then from top to down, we generate the model for each phase, finally we produce a federation and federate rapid development template. 2. Second, if an enterprise intents to paticipate in a existing cooperative project and exchange data with other heterogeneous IS. Thus, we assume an HLA federation has already been created. Here, according to the HLA FEDEP, federate starts to be considered from the second step (Perform Conceptual Analysis) as the reversal scenario 2 shows in fig. 6. Therefore it is not necessary to reverse to the first phase, the reversal can stop at the second phase (Domain scenario systematization). One will only reuse the model of the existing federation to create the model for the federate related to the legacy system of the new participator. Finally, the model of the existing federation and the new federate model are used to generate the code template for the new federate for rapid development.
66
Z. Tu, G. Zacharewicz and D. Chen
6. Conclusion and Future Works Based on the state-of-the-art, we have proposed a new systematic methodology, which is a valuable outcome of the combination of HLA FEDEP & MDA alignment and Model reverse engineering. This methodology provides a new five steps process to develop models of simulation starting from conceptual enterprise models. In addition, it also bridges the gap from concepts to implementation in the field of enterprise modelling by offering a new standardised and reversible approach. This methodology seems promising regarding to real enterprise information system requirement of distribution, federated interoperability and agility of adapt to dynamic context. Compared with other techniques, which can solve the interoperability problem, such as SOA, our methodology is trying to provide a standard service API for all the participants, who can use this API to develop communication agent which adapts to the existing IT system without changing it. Up to now, this work is still in a research process. The methodology presented (each phase of HLA/MDA alignment and the model reversal process) still needs to be refined and detailed. A case study will allow testing the proposed approach in an industrial context.
7. References [1]
IEEE std 1516.2-2000. IEEE Standard for Modeling and Simulation (M&S) High Level Architecture (HLA) - Federate Interface Specification, Institute of Electrical and Electronic Engineers. [2] IEEE std 1516.3-2003. IEEE Standard for Modeling and Simulation (M&S) High Level Architecture (HLA) - Federation Development and Execution Process (FEDEP), The Institute of Electrical and Electronic Engineer. [3] OMG, 2003. MDA Guide Version 1.0.1. Object Management Group, Document number: OMG / 20030601 Available from: www.omg.org/docs/-omg/03-06-01.pdf [accessed 15 June 2009] [4] Andreas T, (2002), Avoiding another Green Elephant—A Proposal for the Next Generation HLA based on the Model Driven Architecture. Proceedings of the 2002 Fall Simulation Interoperability Workshop: 02F-SIW-004 [5] Shawn P, (2003), The Next Step Applying the Model Driven Architecture to HLA. Proceedings of the 2003 Spring. Workshop: 03S-SIW -123 [6] Trbovich S, Reading R, (2005) Simulation and Software Development for Capabilities Based Warfare: An Analysis of Harmonized Systems Engineering Processes. Proceedings Spring Simulation Interoperability Workshop: 05S-SIW-106 [7] Favre L, Martinez L, Pereira C, (2008), MDA-Based Reverse Engineering of Object Oriented Code. SERA’08: 153-160 [8] Favre L, (2008), Formalizing MDA-based Reverse Engineering Processes. SERA’08: 153-160 [9] Zacharewicz G, Chen D, Vallespir B, (2008), HLA Supported, Federation Oriented Enterprise Interoperability, Application to Aerospace Enterprises. Proceedings of 2008 EURO International Simulation Multi-conference: 08E-SIW-074 [10] Meta Object Facility (MOF) Specification v1.4, OMG Document formal/02-04-03, http://www.omg.org/cgi-bin/apps/doc?formal/02-04-03.pdf
Part II
Enterprise Modeling for Enterprise Interoperability
A Meta-model for a Language for Business Process Characterizing Modelling Shang Gao1 and John Krogstie1 1
Department of Computer and Information Science, Norwegian University of Science and Technology, Sem Sælands Vei 7-9, NO-7491 Trondheim, Norway
Abstract. In this paper, a meta-model for the business process characterizing model (BPCM) is defined. The defined meta-model, mainly capturing the syntax and semantics of the business process charactrizing model, is intended to guide the development of business process support systems. In addition, the relation between the SCOR model and the class process in the BPCM meta-model is addressed. Furthermore, the mapping from the BPCM meta-model to BPMN meta-model in a combined framework for developing business process support systems is depicted. Keywords: Meta-model, Business Process Characterizing Model (BPCM), Process Modelling, SCOR
1. Introduction The development of a business process support system is a complicated process that not only requires solving technical problems, but also needs taking the organizational problems related to the business domain into consideration. Different modelling techniques with various purposes and orientations, such as, agent-oriented modelling approach (i*[19]), and process-oriented modelling approach (BPMN [17]), have been proposed and used in developing business process support systems. These approaches have been successfully used in providing some key concepts which are essential to develop business process support systems. However, these modelling techniques often fail in the aspect of providing a modelling approach which can facilitate communications among business stakeholders. Therefore, a good understanding of business domain knowledge is a prerequisite to succeed in developing an effective business process support system. Some articles (e.g. [14] [19] [8]) have pointed out the importance of capturing organizational knowledge and requirements before process modeling design and requirements elicitation.
70
S. Gao and J. Krogstie
Further, with the growing interest in mobile commerce [16], there is an increasing need for methods and techniques that help in supporting process system development in mobile settings. Consequently, it makes the concept of context essential when designing and developing business process support systems, especially in mobile settings. Advanced business support systems are supposed to be able to support users according to the specific context environment. It is believed that there is a tight complementary relationship between activities in process models and context variables. And modelling context information is not a standalone task. It needs to be integrated with high level business modelling and analysis to design and elicit business process systems. Therefore, a new language needs to be developed to deal with the needs mentioned above. As illustrated in [7], one of the main ways of utilizing models is to describe some essential information of a business case informally in order to facilitate communications among stakeholders. In [9], by taking inspiration from this idea, we proposed the business process characterizing model (BPCM), which can be seen as an important early, business-oriented model in a modeling-based project. A BPCM model is characterized by its ability to address the key concepts (actor, goal, context, business domain, etc) involved in a business model development process. BPCM aims to provide an enhanced ability to understand and communicate business processes to all stakeholders involved in the development lifecycle. Such a model shows some essential elements of the business solution to be developed, anchored in business-oriented terminology. The main objective of this paper is to define a BPCM meta-model, mainly capturing the syntax and semantics of the BPCM, which is intended to ensure traceability among different models involved in the development of business process support systems through a combined framework [8]. A meta-model is a model which is used to specify certain features of a model. In this research work, the BPCM meta-model is used to describe the BPCM modelling constructs and relationships of the constructs. The remainder of this paper is organized as follows. Section 2 briefly describes BPCM. Section 3 defines a BPCM meta-model. In section 4, we illustrate the relation between the BPCM meta-model and the SCOR Model. Mapping from the BPCM meta-model to the BPMN meta-model is depicted in section 5. Finally, this paper is concluded in section 6.
2. Business Process Characterizing Model (BPCM) In the course of business process support system development, model developers focus on operational and procedural aspects of process systems, while various business stakeholders are more likely to express different concerns with regard to process models in terms of business oriented concepts. Most process modelling languages, like BPMN [18] or EPC [1], do not offer the necessary support mechanisms to express business oriented concerns in connection with process models. On the one hand, business stakeholders need a simplified model to express their concerns from the organizational perspective easily. On the other hand, process model developers would like to get the business
A Meta-model for a Language for Business Process Characterizing Modelling
71
process system specification in a better modelling language to ease their communications with business stakeholders. Successful business process support system requires the understanding of needs from various stakeholders involved in the business process. Therefore, in order to tackle these problems, we proposed a language for business process characterizing modelling in [9]. BPCM modelling aims to provide an enhanced ability to understand and communicate business processes to all stakeholders involved in the business process development project. The main objective is to assist both business stakeholders and model developers in the development lifecycle. Additionally, the BPCM model can be integrated into a combined framework for development of business process support systems [8], consisting of other modelling techniques, such as goal modelling and process modelling. Table 1 summarizes the general definition of the elements in a business process characterizing model. Table 1. Definition of the elements in BPCM
Element Process Resource Actor Context Business Domain Goal
Process Type
General Definition The business process people want to characterize. This element can be related to a common business process ontology such as SCOR [3]. This element is inspired by the resource concept in the REA framework [13]. This element can clearly address what are consumed and what are gained in a business process. This element describes the people and organizations with different roles involve in a business process. This element can illustrate who are important to which business process. It includes contextual characteristics in terms of locations and networks providing connections between the devices and others. This element classifies the business domain. We tend to link this element to the North American Industry Classification System (NAICS). This element can address what kinds of goals need to be fulfilled in the business process. The goals may be related to operational goals and strategical goals. Operational goals are related to hard-goals, usually covering functional requirements; while strategic goals are related to soft-goals, which set the basis for non-functional requirements. According to REA [11], REA does not model only exchanges but also conversions. Exchange and conversion can be seen as two typical process types.
In order to better illstruate BPCM modelling approach, a small example is provided in Table 2. In the realm of organizing conferences, the main actor is the organizational unit set up to organize the conference. This actor liaises with a number of other organizations to deliver the conference to the participants, for example: the conference proceeding is to be published by a professional publisher a couple of days before the conference. The reason to use a publisher is that having a renowned publication will attract more submissions.
72
S. Gao and J. Krogstie Table 2. BPCM model for producing conference proceedings BPCM Name
BPCM Elements
Publish proceedings with professional publisher
Process
Publish proceedings (ref to SCOR S3 Source Engineer-to-order Product (Proceedings)) Proceedings proposal (including previous acceptance rate for conference, acceptance rate of current conference, conference organizer) Organizing Committee, Publisher, Shipping company PC over LAN/WLAN, internet communication 561920 Convention and Trade Show Organizers 51113 Book Publishers (for publisher) Hard Goals: Proceedings physically delivered to conference organization a couple of days before conference starts(to be able to prepare delegate package) Soft goal: Minimize cost of proceedings Soft goal: Maximize the perceived status of publication Conversion (money for published proceeding)
Resource Actor Context Business Domain Goal
Process Type
Since some elements in the BPCM model refer to other ontologies or systems as presented in the Table 1, a brief description of those concepts and the motivation to incorporte those concepts is provided here. Concerning the element context, there is no universal or absolute definition for context. [5] describes context as “typically the location, identity, and state of people, groups and computational and physical objects”. Context is the reification of the environment, that is, whatever provides a surrounding in which the system operates. People can base their own perceptions or understanding to define context in different ways. In order to better design business process support system, it is crucial to collect and deliver contextual information in a better way. By including context element in a BPCM model, the correspondent business process support system is able to serve people better in mobile computing settings. Recently, W3C has released a draft version of the Delivery Context Ontology (DCO). This ontology constructed in OWL provides a model of characteristics of the environment in which a device interacts with the web or other services. In this research work, we incorporate some key entities of DCO into the element context of BPCM. Some other research work has also started addressing the relationship between context and system development at the requirement level. For instance, [2] investigates the relation between context and requirements at the beginning of goal oriented analysis, and [15] extends the application of the problem frames approach with context monitoring and switching problems. The SCOR model is developed by the supply chain council and aims to describe the operations of various supply chain constructs. It classifies the operations of supply chain as Plan, Source, Make, Deliver and Return. The main advantage of the SCOR model is to facilitate the knowledge sharing and cooperation among the various participants interested in that particular domain of knowledge. Moreover, having a set of standardized ontologies for the domain knowledge of business process support systems development will enhance the
A Meta-model for a Language for Business Process Characterizing Modelling
73
interoperability between the various process support systems. Integrating SCOR with the element process of BPCM for the development of business process support systems will result in a reusable, easy to integrate knowledge repository. REA [11] was originally conceived as a framework for accounting system, but it has subsequently broadened its scope and developed into an enterprise domain ontology. The duality of resource transfer is essential in commerce. It never happens that one agent simply gives away a resource to another without expecting another resource back as compensation. As illustrated in [8], the element resource of BPCM is important in identifying relevant tasks or activities for the construction of process models. For each resource in a BPCM, it should include a message flow which links two associated tasks in a BPMN process model, whereby the source of the message flow connected to the dependee’s task and the destination of the message flow connected to the depender’s task. Last but not least, the North American Industry Classification System (NAICS) is a standard for the collection, tabulation, presentation, and analysis of statistical data describing the U.S. economy. NAICS is based on a production-oriented concept, meaning that it groups establishments into industries according to similarity in the processes used to produce goods or services. Each business process is labeled with a business domain. This is of help for model users to search or retrieve business processes within specific business domain.
3. BPCM Meta-model It is important to note that the BPCM model aims to be an easy to understand modeling language for all business stakeholders and model developers. Most process modeling languages (e.g. BPMN) do not offer the necessary mechanisms to include organizational or contextual concerns associated to a process model. What the BPCM modeling language distinguishes from them is to provide some constructs to tackle those concerns. The aim of this BPCM meta-model is to aid model developers with the various concerns from business stakeholders in designing the desired process models. The BPCM meta-model is described in Figure 1, which presents the major modeling concept and the relationships between them. UML class diagram is used to create the BPCM meta-model. The central class of the meta-model is process. One process may consists of zero or more sub process(es) by the representation of UML compositions. All other main classess can be associated with the central class process. Around the central class, business stakeholders could express different concerns, like required actors, required resources, contextual information, and so on. We use UML generalizations in case of elements extensions (e.g. context, process types). Then, process model developers can take these concerns into consideration when designing process models accordingly. The delivery context ontology mainly focuses on the following three entities: a). environment including information about the location and network, b). software describes whether the delivery context supports certain APIs, document formats, operating systems, etc, c). Hardware provides information about various hardware
74
S. Gao and J. Krogstie
capabilities including display, input, memory, etc. For the class context, we do not attempt to cover all entities above. We focus on two major aspects: location and network information. For example, a user using its device is connected to an information system through a wireless network or wired network. Mobile workers need to work in various locations (e.g. at home, in the office, on the way). Business process scenario itself is a complex, dynamic network that involves many business stakeholders. Integrating SCOR with the BPCM meta-model for the business process development process will facilitate knowledge sharing and communication among the various parties involved in the processes. As illustrated in Figure 1, we have incorporated process best practices, process levels from SCOR into the BPCM meta-model. The BPCM meta-model can also be transformed to OWL-based ontology. The ontology is built by defining classes, subclasses, properties, and instances which present the elements in BPCM meta-model. The BPCM ontology classes in the class browser is shown in Figure 2. The Ontologies is developed using Protégé software. Protégé is a free open-source software tool that was developed at Stanford University for building ontologies. Since the BPCM meta-model is centered with the class process, all other constructs are constructed relatively to process. The key role of the created ontology here is to form a repository to store various BPCM models. In this way, the existing BPCM models in an ontology repository may become reference models for various purposes. In addition, the ontology can also be seen as a reusable knowledge base for sharing and retrieving purposes in the future development. For instance, the class business domain can be used as a key for the querying purpose. Relevant information from similar areas can be retrieved by querying keywords of specific business domain.
Figure 1. BPCM Meta Model
A Meta-model for a Language for Business Process Characterizing Modelling
75
Figure 2. BPCM Ontology Classes
4. Relation Between SCOR and Process in BPCM Meta-model SCOR is a process reference model designed for effective communications among supply chain partners. SCOR integrates concepts of business processes, benchmarking, and best practices into a cross-functional framework. From business process reengineering perspective, the SCOR model builds a hierarchy of supply chain processes, which can be divided into three levels of details [3]: process type, process category, and process element. The process element level provides and documents enough details of process specifications, consisting of input and output parameters, process performance metrics, and best practices. Consequently, these detailed specifications can convey a better understanding of the relevant processes in BPCM which fits with the purpose of including BPCM model in the process support systems development lifecycle. The SCOR model does not follow any of the standardized or well structured business process modeling techniques such as BPMN or UML activity diagram. In contrast, the SCOR model provides the capability for business stakeholders to extract the existing supply chain knowledge, such as resources required for a specific process. In addition, the SCOR model also provides a mechanism for various users to reuse and share concepts and knowledge in a supply chain process. Having the SCOR model integrated with the BPCM meta-model for business process support systems development will result in a reusable, easy to integrate knowledge base. The SCOR model can be represented as a hierarchy of supply chain processes as depicted in the upper layer in Figure 3, where the level 1 and level 2 are for
76
S. Gao and J. Krogstie
representing more generic issues, such as planning and making, and the level 3 is for representing specific processes. Since the SCOR model is based on business process reengineering, this makes SCOR a process centric model. The processes in the SCOR model are the processes that are found in any supply chain. Concerning the relation between SCOR and the element process in the BPCM meta-model, each process element in the level 3 of the SCOR model can map to one process in the BPCM model as presented in Figure 3. This mapping aims to transform the detailed process element information in level 3 of the SCOR model to relevant elements in the BPCM meta-model. In addition, a process in a BPCM model may consist of several sub processes. The process elements information defined in the level 3 of the SCOR model might not be practical in terms of explicitly usefulness and utilization with respect to technical process models construction. However, having this information in place forms a good reusable knowledge base which facilitates communications between business stakeholders and model developers. Furthermore, the SCOR model makes sure that the relevant process elements in the level 3 from the organizational point of view are appropriately placed in the BPCM model in terms of various processes.
Figure 3. Relation between SCOR and Process in BPCM meta-model
A Meta-model for a Language for Business Process Characterizing Modelling
77
5. Mapping from BPCM Meta-model to BPMN Meta-model In this section, we illustrate the relation between the elements in the BPCM metamodel and the operational level process model in a combined framework [8] for development of business process support systems. In this combined framework, we consider a relatively informal model, more specifically BPCM here, which can ease the communication and cooperation between business stakeholders and technical model developers, as a starting point for developing a business process support system. In [12], they also argued that it is often beneficial to start a modeling-based project with an informal model and then develop the visual models. And then the BPCM models will be derived and developed into visual process models and executable models. Lastly, those models can be used as inputs for deriving a candidate IT system. The combined framework covering coarse grained business process characterizing modelling, and goal modelling and process modelling provides several benefits. It supports users to view the system from different perspectives. It also provides a mechanism for mapping of correspondences between meta-models of different models. Since BPMN has relatively higher expressiveness and ability to map directly to executable process languages such as business process execution language (BPEL) [10] and XPDL [6] compared to other process modeling notations, we select BPMN as the candidate notation for the operational level process model in the combined framework. Based on the BPCM meta-model proposed in section 3 and the BPMN 1.0 meta-model proposed by WSPER Group1, which is a class diagram that shows the elements of the BPMN language and their relationships, we analyze the mapping between those two models by considering Curtis framework on process modelling approach [4] which is based on four basic aspects: functional aspect, behavioral (control) aspect, organizational aspect, and informational aspect. BPCM: actor maps to BPMN: pool or lane, which covers organizational aspect. Likewise, BPCM: resource map to BPMN: data objects, which represents informational aspect. Concerning functional aspect, BPMN: task can be derived from BPCM: resource and actor in terms of complementary requirement table approach defined in [8]. The aspect which is least covered by the BPCM meta-model is the behaviroal (control) perspective for enacting business processes. The input and output parameters of the process element in the level 3 of the SCOR model may have implicitly effort on determining the order of activities and control flows. Refined BPCM meta-model with some extra SCOR properties and entities may help resolve this issue, which will result in better mappings between two metamodels. Further, we find that the traceability of the BPCM model to the BPMN model is improved in terms of the identified overlaps between two meta-models.
1
The BPMN meta-model is available at: http://www.ebpml.org/wsper/wsper/bpmn1.0.jpg
78
S. Gao and J. Krogstie
6. Conclusion In this paper, we describe a BPCM meta-model, which provides a foundation for building business process support systems. And the BPCM ontology classes on the type level are built. In addition, the relation between the SCOR model and the class process in the BPCM meta-model is addressed. Furthermore, the mapping from the BPCM meta-model to BPMN meta-model is depicted. However, it must be admitted that the usage and evaluation of the BPCM meta-model in the combined framework is currently quite limited since we have not tested it in some case studies. Future research will apply the BPCM meta-model and the combined framework in connection to supporting a loosely organized conference series.
7. References [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]
[13] [14] [15]
Aalst, W.v.d.: Formalization and Verification of Event-driven Process Chains. Information and Software Technology. 41 (10), 639-650 (1999) Ali, R., Dalpiaz, F. and Giorgini, P.: A Goal Modeling Framework for Selfcontextualizable Software (eds.). 29, 326-338. LNBIP, Springer (2009) Council, S.-c. SCOR Model 8.0 Quick Reference Guide, (2006) Curtis, B., Kellner, M.I. and Over, J.: Process modeling. Commun. ACM. 35 (9), 7590 (1992) Dey, A.K., Abowd, G.D. and Salber, D.: A conceptual framework and a toolkit for supporting the rapid prototyping of context-aware applications. Human-Computer Interaction. 16 (2), 97-166 (2001) Fischer, L.: workflow handbook 2005. Workflow Management Coalition (WfMC) (2005) Fowler, M.: UML Distilled: A Brief Guide to the Standard Object Modeling Language. Addison-Wesley, Reading, MA (2003) Gao, S. and Krogstie, J.: A Combined Framework for Development of Business Process Support Systems. (eds.) The Practice of Enterprise Modeling. 39, 115-129. LNBIP, Springer (2009) Gao, S. and Krogstie, J.: Facilitating Business Process Development via a Process Characterizing Model. In: International Symposium on Knowledge Acquisition and Modeling 2008. IEEE CS (2008) Havey, M.: Essential Business Process Modeling. O'Reilly Media, CA (2005) Hruby, P.: Model-Driven Design Using Business Patterns. Springer-Verlag New York (2006) Maiden, N.A.M., Jones, S.V., Manning, S., et al.: Model-Driven Requirements Engineering: Synchronising Models in an Air Traffic Management Case Study. In: Persson, A. and Stirna, J. (eds.) CAISE 2004. LNCS vol. 3084, pp. 368-383. Springer, Heidelberg (2004) McCarthy, W.E.: The REA accounting model: a generalized framework for accounting systems in a shared data environment. 57, 554-578 (1982) Regev, G. and Wegmann, A. Defining Early IT System Requirements with Regulation Principles: The Lightswitch Approach Proceedings of the Requirements Engineering Conference, 12th IEEE International, IEEE Computer Society, (2004) Salifu, M., Yu, Y. and Nuseibeh, B.: Specifying Monitoring and Switching Problems in Context. In: RE 2007. IEEE CS Press (2007)
A Meta-model for a Language for Business Process Characterizing Modelling
79
[16] Siau, K., Lim, E.-P. and Shen, Z.: Mobile Commerce – Promises, Challenges, and. Research Agenda. Journal of Database Management. 12 (3), 4-13 (2001) [17] White, S.: Business Process Modeling Notation Version 1.0. Business Process Modeling Initiative (BPMI.org) (2004) [18] White, S.A. Introduction to BPMN, (2005) [19] Yu, E.: Modelling strategic relationships for process reengineering. PHD Thesis, University of Toronto (1996)
A Tool for Interoperability Analysis of Enterprise Architecture Models using Pi-OCL Johan Ullberg1, Ulrik Franke1, Markus Buschle1 and Pontus Johnson1 1
Industrial Information and Control Systems, KTH Royal Institute of Technology, Osquldas v. 12, SE-10044 Stockholm, Sweden
Abstract. Decision-making on enterprise-wide information system issues can be furthered by the use of models as advocated by the discipline of enterprise architecture. In order to provide decision-making support, enterprise architecture models should be amenable to analyses. This paper presents a software tool, currently under development, for interoperability analysis of enterprise architecture models. In particular, the ability to query models for structural information is the main focus of the paper. Both the tool architecture and its usage is described and exemplified. Keywords: Enterprise Architecture, Probabilistic Relational Models, Software tool, Interoperability
1. Introduction During the last decade, enterprise architecture has grown into an established approach for holistic management of information systems in an organization. Enterprise architecture is model-based, in the sense that diagrammatic descriptions of the systems and their environment constitute the core of the approach. A number of enterprise architecture initiatives have been proposed, such as The Open Group Architecture Framework (TOGAF) [1], Enterprise Architecture Planning (EAP) [2], the Zachman Framework [3], and military architectural frameworks such as DoDAF [4] and NAF [5]. What constitutes a “good” enterprise architecture model has thus far not been clearly defined. The reason is that the “goodness” of a model is not an inherent property, but contingent on the purpose the model is intended to fill, i.e. what kind of analyses it will be subjected to. For instance, if one seeks to employ an enterprise architecture model for evaluating the performance of an information system, the information required from the model differs radically from the case when the model is used to evaluate system interoperability.
82
J. Ullberg, U. Franke, M. Buschle and P. Johnson
Enterprise architecture analysis is the application of property assessment criteria on enterprise architecture models. For instance, one investigated property might be the information security of a system and a criterion for assessment of this property might be “If the architectural model of the enterprise features a communication link with high availability, then this yields a higher level of interoperability than if the availability is low.” Criteria and properties such as these constitute the theory of the analysis and may be extracted from academic literature or from empirical measurements. This theory can be described using probabilistic relational models (PRMs) [6] which will be further detailed in section 1.3 Many interoperability concerns are related not only to various attributes of the architecture model but rather to the structure of the model, e.g. that two communicating actors need to share a language for their communication. With the actors and languages being entities in the metamodel, this property corresponds to ensuring that particular relationships exist in the architecture model instance. This paper presents a software tool under development for the analysis of enterprise architecture models. This tool extends previous versions of the tool [7][8] and the main contribution of this article is to illustrate how to query the architecture models for structural information such as the language compatibility as described above. This extension is based on the Object Constraint Language (OCL) [9] and is further detailed in section 1.3. The enterprise architecture frameworks described above generally suffer from the lack of methods for evaluating the architectures [10]. A number of enterprise architecture software tools are available on the market, including System Architect [11] and Aris [12]. Although some of these provide possibilities to sum costs or propagate the strategic value of a set of modeled objects, none have significant capabilities for system quality analysis in the sense of ISO-9126 [13], i.e. analysis of non-functional qualities such as reliability, maintainability, etc. However, various analysis methods and tools do exist within the software architecture community, including the Architecture Tradeoff Analysis Method (ATAM) [14] and Abd-Allah and Gacek [15]. In particular, various approaches such as LISI [16] and i-Score [17] have been suggested for assessing interoperability. However, these are generally not suitable in the enterprise architecture domain. Assessment Scoping
Evidence Collection Model Builder Function
Analysis Structural Analysis Function
provid ed by
Provid ed by 1..*
Provides 1 System
Administrat ed by 0..*
Administr ates 1
0 . . *
0.7 0.2 0.1 <Source id="Erik Johansson"/> <source id="Pontus Johnson"/>
Error locate with
System administrator
MTTF
Responsetime
MTTR
Repairtime
PRM
used by
Customer S upport : Funct ion
Fault Management : Function
provid ed by
Availiability
Availability
Uses 0 . . *
System Availiability
Calculation Function
Evidence.Interview.Juliet M e d i u m
provides administ r ated by
provides CRM Syst em : Syst em
Maintenance system : System
Availability
Availability
Reliability
Reliability
administr ates with
administrat es
Juliet : System administrat or Respons iveness Evidence. Document.Log H i g h
administ r ated by
Evidence. Document. M Log e d i u m
administrat es
Evidence.Observation. Juliet H i g h
Experience
Joseph : System adminis trator Responsiveness
Evidence.Observat ion.Joseph H i g h
Ex perience
Evidence.Interview.Juliet H i g h
E videnc e.I nterview.Joseph H i g h
Scenarios
Evidence
Instantiated PRM
Fig. 1. The process of enterprise architecture analysis with three main activities: (i) setting the goal, (ii) collecting evidence and (iii) performing the analysis
A Tool for Interoperability Analysis of Enterprise Architecture Models using Pi-OCL
83
2. Process of Enterprise Architecture Analysis Enterprise architecture models have several purposes. Kurpjuweit and Winter [18] identify three distinct modeling purposes with regard to information systems, viz. (i) documentation and communication, (ii) analysis and explanation and (iii) design. The present article focuses on the analysis and explanation since this is necessary to make rational decisions about information systems. An analysiscentric process of enterprise architecture is illustrated in Fig. 1 above. In the first step, assessment scoping, the problem is described in terms of one or a set of potential future scenarios of the enterprise and in terms of the assessment criteria (the PRM in the figure) to be used for scenario evaluation. In the second step, the scenarios are detailed by a process of evidence collection, resulting in a model (instantiated PRMs, in the figure) for each scenario. In the final step, analysis, quantitative values of the models’ quality attributes are calculated, and the results are then visualized in the form of enterprise architecture diagrams. More concretely, assume that a decision maker in an electric utility is contemplating the changes related to the measurement of customer electricity consumption. The introduction of automatic meter reading would improve the quality of the billing process and allow the customers to get detailed information about their consumption. The question for the decision maker is whether this change is feasible or not. As mentioned, in the assessment scoping step, the decision maker identifies the available decision alternatives, i.e. the enterprise information system scenarios. Also in this step, the decision maker needs to decide on how to determine how this scenario should be evaluated, i.e. the assessment criteria, or the goal of the assessment. Oftentimes, several quality attributes are desirable, but we simplify the problem to the assessment of interoperability. During the next step, to identify the best alternative, the scenarios need to be detailed to facilitate an analysis of them. Much information about the involved systems and their organizational context may be required for a good understanding of their future interoperability. For instance, it is reasonable to believe that a reliable medium for passing messages would increase the probability that communication is successful. The availability of the message passing system is thus one factor that can affect the interoperability and should therefore be recorded in the scenario model. The decision maker needs to understand what information to gather, and also ensure that this information is indeed collected and modeled. When the decision alternatives are detailed, they can be analyzed with respect to the desirable property or properties. The pros and cons of the scenarios then need to be traded against each other in order determine which alternative should be preferred.
3. An Enterprise Architecture Analysis Formalism A probabilistic relational model (PRM) [6] specifies a template for a probability distribution over an architecture model. The template describes the metamodel M for the architecture model, and the probabilistic dependencies between attributes of
84
J. Ullberg, U. Franke, M. Buschle and P. Johnson
the architecture objects. A PRM, together with an instantiated architecture model I of specific objects and relations, defines a probability distribution over the attributes of the objects. The probability distribution can be used to infer the values of unknown attributes. This inference can also take into account evidence on the state of observed attributes. A PRM Π specifies a probability distribution over all instantiations I of the metamodel M. As a Bayesian network [6] it consists of a qualitative dependency structure, and associated quantitative parameters. The qualitative dependency structure is defined by associating attributes A of class X (A.X) with a set of parents Pa(X.A), where each parent is an attribute, either from the same class or another class in the metamodel related to X through the relationships of the metamodel. For example, the attribute satisfied of the class Communication Need may have as parent CommunicationNeed.associatedTo.communicatesOver.isAvailable, meaning that the probability that a certain communication need is satisfied depends on the probability that an appropriate message passing system is available. Note that a parent of an attribute may reference a set of attributes rather than a single one. In these cases, we let X.A depend probabilistically on an aggregated property over those attributes constructed using operations such and AND, OR, MEAN etc. Considering the quantitative part of the PRM, given a set of parents for an attribute, we can define a local probability model by associating a conditional probability distribution with the attribute, P(X.A |Pa(X.A)). For instance, P(CommunicationNeed.satisfied=True|MessagePassingSystem.isAvailable=False) =10% specifies the probability that communication need is satsified, given the availability of the message passing system. 3.1. Pi-OCL PRMs do not, however, provide any means to query the models for structural information such “as given two actors with a need to communicate, do these actors have a common language (modeled as a separate object)?” The Object Constraint Language (OCL) is a formal language used to describe constraints on UML models. Writing these types of constraints in natural language would lead to ambiguities. In order to resolve this, OCL provides a means to specify such constraints in a formal language without the need for extensive mathematical knowledge. OCL expressions typically specify invariant conditions that must hold for the system being modeled or queries over objects described in a model. [9] This ability to query models would be of great benefit to interoperability analysis. OCL is, however, a side effect free language, so that the application of an OCL statement cannot change the content of the model. Furthermore it is deterministic and thus incapable of allowing uncertainty in the analysis. This section briefly describes how these two aspects of OCL are addressed by the extension to probabilistic imperative OCL or Pi-OCL for short. For a more comprehensive treatment see [19]. For the language to become imperative, i.e. to be able to change the state of the model, the introduction of an assignment operator is necessary. Turning OCL into a probabilistic language also requires redefinition of all operations in OCL, which is accomplished through the mapping of each operation to a Bayesian network and then combining these networks into larger
A Tool for Interoperability Analysis of Enterprise Architecture Models using Pi-OCL
85
networks corresponding to a complete Pi-OCL statement. For the sake of the analysis it is also necessary to introduce an existence attribute E in all classes and relationships corresponding to the probability that the class or relationship exists. Each expression views the model from the perspective of a context object C. The probability that an instantiated object O and its attributes O.A exist are thus not only dependent of O.E but also the existence of the relationships from the context object C to O. This context dependent existence is a key factor in the definition of all other OCL operations. To provide an example of how the operations are defined the following is a description of the equality operator 2 : . Since the original OCL equality operator is defined using the deterministic type Boolean, this operation needs to be refined. The probability that a given object o1 equals some other object o2, o1=o2 is calculated as follows: …
. , 0
…
.
Where … . , … . is the joint probability that there is a link from the context object to each of the objects o1 and o2 and id(object : OclAny) : Integer is a function that returns a unique identifier for each object. For a more comprehensive treatment of all of OCL statements in the Pi-OCL setting see [19]. The probability model of an attribute in a PRM expressed in terms of parent attributes can be replaced by Pi-OCL statements. Such statements allow not only attributes to constitute the parents of an attribute but also various aspects pertaining to the structure of the model. A PRM coupled with Pi-OCL statements thus constitutes a formal machinery for calculating the probabilities of various architecture instantiations. This allows us to infer the probability that a certain attribute assumes a specific value, given some (possibly incomplete) evidence of the rest of the architecture instantiation.
4. Design of the Tool Here a software tool supporting the enterprise architecture analysis process is outlined. The structural design of the tool is based upon the three basic processes illustrated in Fig. 1. Relating to the previous section, the first process step concerns the identification of the decision alternatives and the goals (assessment criteria). An example of a goal is to maximize the interoperability of an IT landscape. Goals are codified in a PRM, which also represents how various attributes and the structure of the model affect the goals (through the probability model and Pi-OCL statements). For instance, the PRM might state that the availability of the message passing system will affect the interoperability of the scenario. The Scenarios are not detailed in this step, but only given a name. In the second process step, the scenarios are elaborated. An example of a scenario might be to choose vendor X for the automatic meter reading system. In order to assess whether this is a better scenario than the one based on vendor Y,
86
J. Ullberg, U. Franke, M. Buschle and P. Johnson
more information is required. For instance we might need to detail the communication mediums employed by the respective vendors. Collected information on matters like these is called Evidence, and the process of evidence collection is supported by the tool. From the evidence, the Model Builder Function creates an instantiated PRM, which is a comprehensive enterprise architecture scenario model. The model thus typically contains instantiations of entities such as actor, message passing system, language, etc. Many times, the collected evidence will not be sufficient to allow full certainty of the values of entity attributes (for instance the attribute availability of the entity message passing system). They are therefore defined as random variables, allowing the representation of uncertainty. Recall that an important purpose of enterprise architecture models is to answer relevant questions, such as whether the interoperability of scenario A is higher than in scenario B. Oftentimes, it is not possible to directly collect information about properties such as interoperability, but it is possible to collect evidence pointing in a certain direction (e.g. information on the availability of the message passing system) and create models in which the structure of the model can be used for such evidence. Based on the created architecture model the structural analysis function use the Pi-OCL statements defined in the PRM to evaluate various structural concepts of the architecture. This is done by mapping the statements to Bayesian networks, evaluating these networks and writing the result back to attributes of the architecture model. Employing Bayesian theory once again, the Calculation Function calculates the values of those attributes that could not be credibly determined directly. The tool employs the collected evidence, the result of the structural analysis as well as the causal relationships specified in the PRM as input to these calculations. Central artifacts in enterprise architecture frameworks and tools are graphical models. The instantiated PRMs containing the enterprise architecture scenarios is therefore employed for displaying the results and the tool allows various views of the models. 4.1. Architecture of the Tool The tool is implemented in Java and uses a Model-View-Controller architecture, thus having these three main parts, illustrated in Fig. 2. The data model for PRMs and instantiated PRMs is specified in XSD files. The data binding tool Castor [20] allows simple marshalling and unmarshalling of XML models to and from java objects (the Model). The model elements are contained by the Widgets of the Net-Beans Visual Library that also update the view when the model changes. Model operations are controlled by a number of internal tools. This essentially corresponds to the functions of the design outlined above and a set of supporting tools. These internal tools, acting as controllers, provide uniform access to their functionality as they are all implemented in a common way, using the singleton pattern. One internal tool of particular interest here is the Pi-OCL evaluation tool that, based on the structure of the model, can perform various assessments of the
A Tool for Interoperability Analysis of Enterprise Architecture Models using Pi-OCL
87
architecture. At the core of the tool is a Pi-OCL interpreter created using SableCC [21]. SableCC create an abstract syntax tree representation of Pi-OCL statements based on the grammar and provides a skeleton for traversal of the syntax tree using the visitor pattern. This skeleton is then refined to evaluate the result of the Pi-OCL statements. As this analysis is probabilistic each of the nodes in the abstract syntax tree are evaluated using Bayesian networks by employing the Smile library [22] for calculations. The results are then written back to attributes of the model. The view is implemented as a part of the JApplication framework. The view is in charge of handling all user interactions that are not concerned with the drag-anddrop modeling features of the scene. Several methods handle button and menu actions. Also, loading and saving tools are called by the view. Model
Controller
XSD PRM
Java PRM
XSD iPRM
Java iPRM
View
Fig. 2. High level architecture of the tool, illustrating the main components. "iPRM" is shorthand notation for instantiated PRM
5. Employing the Tool for Interoperability Analysis In this section a short example of the employment of the tool will be outlined. Interoperability is defined by IEEE as the ability of two or more systems or components to exchange information and use the information that has been exchanged [23]. This can be seen as a communication need and the interoperability analysis would correspond to ensuring that this need is satisfied. Consider the following metamodel for interoperability analysis where two or more Actors share a Communication Need. The actors communicate over a message passing system, e.g. the internet and encode the messages sent over the message passing system in a format, the language. On such a metamodel and interoperability definition the following very simple theory of interoperability can be expressed: 1) for interoperation to take place there need to be a path for message exchange between the actors of a communication need. 2) the actors must share at least one language for expressing their communication and finally 3) the message passing system
88
J. Ullberg, U. Franke, M. Buschle and P. Johnson
Fig. 3. A sample PRM for interoperability analysis detailing the important entities and relationships needed for the analysis
these actors use must be available This theory can be expressed as a PRM using the tool, cf. Fig. 3 where the abovementioned entities are modeled. The Communication Need class contains three attributes, the satisfied attribute corresponding to the goal of the analysis and two attributes corresponding to statement 1 and 2 of the theory. Since the third statement was concerned with the availability of the message passing system this is also included as an attribute of the message passing system class. Turning to the probability model of the PRM the first two statements in the theory are based on the structure of the architecture and can be expressed using with the following Pi-OCL statements: Context: CommunicationNeed self.pathExist := self.associatedTo->forAll(a1 : Actor, a2 : Actor | a1 <> a2 implies a1.communicatesOver.communicatesOver-1 -> exists(a2)) self.LanguageMatch := self.associatedTo->forAll(a1 : Actor, a2 : Actor | a1 <> a2 implies a1.uses -> exists(l:Language | a2.uses->exists(l)) As can be seen from these statements the result of the Pi-OCL evaluation is assigned to two of the attributes of the class communication need. These attribute need to be aggregated and combined with the third statement in the theory, that pertaining to the availability of the message passing system. This can be expressed in terms of parent attributes of CommunicationNeed.satisfied, the goal of the analysis. The parents of this attribute thus are: CommunicationNeed.pathExists, CommunicationNeed. languageMatch and CommunicationNeed.associatedTo. communicatesOver.isAvailable, see the solid arrows in the PRM of Fig. 2 . Turning to the quantitative part of the probability model the theory states that all these three criteria must be met for the communication need to be satisfied, an AND operation can thus be employed for aggregation.
A Tool for Interoperability Analysis of Enterprise Architecture Models using Pi-OCL
89
Fig. 4 depicts the concrete modeler where the architectural model is created based on the PRM. This means that specific instances of the abstract concepts are created to reflect the scenario at hand. By entering evidence on the states of the attributes and using the structural analysis function it is possible to use PRM inference rules to update the model to reflect the impact of the architecture and the evidence. The user can thus find updated probability distributions for all attributes in the model.
Fig. 4. An instatiated PRM for the modeled scenario
In this example we have a Communication Need get meter reading between the Actors Billing System and Meter Reading System. These are connected using a X.25 leased line of type message passing system. The meter reading system uses two languages, the common information model (CIM) and EDIEL whereas the billing system only use EDIEL Entering information regarding the availability, of the message passing system and running both the structural analysis and the inference will result in the prediction of a interoperability value for the modeled scenario.
6. Conclusions In this paper, a tool for analysis of enterprise architecture scenarios with a particular focus on interoperability assessments is outlined. The tool, currently under development, allows specification of the assessment theory in terms of a metamodel and a probability model encoded as a PRM with Pi-OCL statements. The Pi-OCL statements are used for structural analysis of the architecture. Based on the metamodel it is possible to model the architecture scenarios and using the theory assesses the interoperability of the scenario. Information system decision making is supported by allowing quantitative comparisons of the qualities, such as interoperability, of possible future scenarios of the enterprise information system and its context.
90
J. Ullberg, U. Franke, M. Buschle and P. Johnson
7. References [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23]
The Open Group. The Open Group Architecture Framework, Version 8, 2005 Spewak, S.H., Hill. S.C., Enterprise Architecture Planning. Developing a Blueprint for Data, Applications and Technology, John Wiley and Sons, 1992 Zachman, J., A framework for information systems architecture, IBM Systems Journal, 26(3), 1987 DoD Architecture Framework Working Group, “DoD Architecture Framework” Version 1.0, 2003 NAF, “NATO C3 Technical Architecture”, Volume 1-5, Version 7.0, Allied Data Publication 34, 2005 L. Getoor, N. Friedman, D. Koller, A. Pfeffer, and B. Taskar. Probabilistic relational models. MIT Press, 2007. Johnson, P., Johansson, E., Sommestad, T. Ullberg, J., A Tool for Enterprise Architecture Analysis, Proceedings of the 11th IEEE International Enterprise Computing Conference (EDOC 2007), 2007 Ekstedt, M. et al. A Tool for Enterprise Architecture Analysis of Maintainability, Proc. 13th European Conference on Software Maintenance and Reengineering, 2009 Object Management Group Object Constraint Language specification, version 2.0 formal/06-05-01, 2006 Chen, D. et al., Architecture for enterprise integration and interoperability: Past, present and future, Comput Industry (ind), 2008 IBM, Rational System Architect, http://www-01.ibm.com/software/awdtools/ systemarchitect/, accessed: Dec 2009 Scheer, A.-W., Business Process Engineering: Reference Models for Industrial Enterprises, 2nd ed., Springer-Verlag, 1994 International Organization for Standardization/International Electrotechnical Commission, “International Standard ISO/IEC 9126-1: Software engineering – Product quality – Part 1: Quality model,” ISO/IEC, Tech. Rep., 2001. Clements, P., R. Kazman, M. Klein, “Evaluating Software Architectures: Methods and Case Studies”, Addison-Wesley, 2001 Gacek, C., “Detecting Architectural Mismatch During System Composition”, PhD. Thesis, University of Southern California, 1998 Kasunic, M., Anderson, W., “Measuring Systems Interoperability: Challenges and Opportunities” Technical Note, CMU/SEI-2004-TN-003, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, 2004. Ford, T., Colombi, J., Graham, S., Jacques, D., “The Interoperability Score”, Proceedings of the Fifth Annual Conference on Systems Engineering Research, Hoboken, NJ, 2007 Kurpjuweit, S., Winter, R.: Viewpoint-based Meta Model Engineering. In Proceedings of Enterprise Modelling and Information Systems Architectures (EMISA 2007), Bonn, Gesellschaft für Informatik, Köllen, pp. 143-161, 2007 Franke U. et. al, π-OCL: A Language for Probabilistic Inference in Relational Models (2010) to be submitted ExoLab Group, The Castor Project, http://www.castor.org/ accessed Dec. 2009 Gagnon, É., SableCC, an Object-Oriented Compiler Framework, Master Thesis, McGill University Montreal, 1998 Decision Systems Laboratory of the University of Pittsburgh, SMILE, http://genie.sis.pitt.edu/ accessed Dec. 2009 IEEE, Standard Glossary of Software Engineering Terminology. Std 610.12-1990, The Institute of Electrical and Electronics Engineers, New York, 1990.
A UML-based System Integration Modeling Language for the Application System Design of Shipborne Combat System Fan Zhiqiang1, Gao Hui2, Shen Jufang1, Zhang Li1 1 2
Dept. of Computer Science and Technology, BeiHang University, Beijing, P.R.China Systems Engineering Research Institute, China State Shipbuilding Corporation, Beijing, P.R.China
Abstract. The Shipborne combat system (SCS) includes many application systems. The integration of application systems is necessary because they are distributed and need to interoperate with each other. For such integration, an integration model needs to be developed. Firstly, the integration framework of application systems of SCS is discussed, which involves three layers: data integration, function integration and workflow integration. Secondly, integration metamodel based on the framework is introduced. Data, application system, function, component, workflow and their relationships are explained in detail. Finally, a system integration modeling language for application system design (SIML4ASD) based on the metamodel is defined by extending UML using profile mechanism. SIML4ASD is easy to learn, use and understand for the system designers and can be used to describe integration models clearly and exactly in multi-view. Keywords: integration framework; integration metamodel; SIML4ASD; UML
1. Introduction The Shipborne Combat System (SCS) is a system of personnel, weapons and devices used to execute early-warning, tracking, communications, navigation, target identification, data processing, threaten assessment, and control various shipborne weapons against the enemy [1]. SCS includes hardware devices (e.g. computers and switch) and software systems (e.g. OS and database). As the software technology has become more and more mature, there are more and more application systems. These application systems are supporting the combat business, and play an important role in SCS. Application systems are distributed on different hardware devices and they work in collaboration to complete combat tasks. There is a need of interoperation among them. Therefore, the integration of application
92
F. Zhiqiang, G. Hui, S. Jufang and Z. Li
systems is very important in their design. Three characteristics of application systems should be considered: 1) there are large amount of data exchanges between application systems when they carry out a combat task collaboratively. 2) different application systems have different functions but some of them have several identical functions. Some times, the functions of system may be changed dynamically. Hence SCS is usually designed to consist of functional blocks and application system is the composition of those blocks. Functions are user-oriented and thus, do not fit to be used as system development guide. SCS is usually designed and developed using component-based technology. Functions are the composition of components. Therefore, for the system design and dynamic function change, the relationship between application system, function and component needs to be established; 3) in order to improve efficiency and achieve automation, part of or whole business processes are designed as workflow which is executed by application systems automatically. The actual activities of workflow are executed by components. Therefore, the relation of workflow and components needs to be established when designing a workflow. Besides that, the features of workflow in SCS should also be considered, e.g. some activities have time constraint and/or cannot be interrupted when being executed. Because of these three characteristics of SCS, application systems are usually integrated by three-layer (data layer, function layer and workflow layer) framework. Data, application system, function, component, workflow and the relationships between these layers need to be described clearly in integration model. However, existing modeling languages are not fully capable of describing the integration model. For example, IDEF can be used to describe system and function using IDEF0 [2], data using IDEF1X [3] and workflow using IDEF3 [4], but it cannot afford to describe the components. UML [5] can be used to describe workflow using activity diagram, data using class diagram and component using component diagram, but the consumption or production relationship between data and component cannot be established. Moreover, the features of SCS (e.g. time constraint) can not be reflected in the workflow model described using UML or IDEF. Thus a new system integration modeling language (SIML) for description of application system integration model and communication of designers is necessary.
2. Application System Integration: Framework and Layers Generally speaking, system integration can be divided into several layers. Deng [6] and Wang [7] proposed a three-layer integration framework of information system which consists of Network layer, Data Layer and Application Layer. Zhang [8] suggested a conceptual framework which consists of five layers, i.e. physical, data, application, business process/functionality and presentation. Edward and Jeffrey’s framework for business integration divided integration into two layer: system and organizational layer, and subdivided system integration into data, application and business process integration [9]. Giachetti gave a framework of enterprise information integration which involves network, data, application and process integration [10]. Drawing on these results, we propose a hierarchical integration
A UML-based System Integration Modeling
93
framework presented in Fig. 1 for the integration of application systems based on the three features mentioned in section I. Application System B
Workflow
Workflow Integration
Function
Function
Data
Data
Integration
Integration
Application System A
Fig. 1. A Integration Framework of Application Systems
Integration at Data Layer: the data layer lays a strong basis for the integration of application systems. Data integration virtually associates the data of different systems and provides the application system with data in a uniform format. Integration at Function Layer: the integration at this layer helps to understand the function of application system and the component realizing specific function. The function integration mainly aims at addressing the composition of components. Integration at Workflow Layer: workflow is the computerised facilitation or automation of a business process, in whole or part [11]. The integration of which asks for the cooperation of different application systems and their compliance with the workflow logic. The framework presents not only horizontal integration, but also vertical integration. Integration between data layer and function layer occurs when a component produces or consumes data. Integration between function layer and workflow layer happens when component executes activities of workflow.
3. Integration Metamodel of Application Systems The main elements involved in the integration framework are: data, application system, function, component and workflow. The conceptual model is showed in Fig. 2. Workflow consists of activities. Activity is executed by component with data consumption or production. Application system participating in the execution of workflow includes functions implemented by components. Based on the integration framework, detailed metamodel is introduced as follows. 3.1. Metamodel at Data Layer The main elements and relationship in the metamodel are descripted in Fig. 3. Data is composed by DataItem related with Type which can be generalized as ConstructedType, SimpleType and CollectionType. A SimpleType is a fixedlength type. CollectionType means a collecton of any type. ConstructedType refers to the type constructed by other types, and Data itself is a kind of ConstructedType.
94
F. Zhiqiang, G. Hui, S. Jufang and Z. Li
Data has zero or more DataInstance. The relationship between Data and DataInstance is Instantiation. The relationships of Data include Generatlization, Agregation and Composition with the same defination in UML [5]. DataDomain is the classification of Data. A Data can only be in one DataDomain.
Fig. 2. Conceputal Model of Application System Integration
3.2. Metamodel at Function Layer The model showed in Fig. 4 explains the relationships among Application System, Function, Component and Data. ApplicationSystem refers to the software system support combat business in SCS. Different ApplicationSystems may have serveral same Functions. Function is the decomposition of application system from users’ view. It cannot be used as system development guide, the application system is decomposed into components from the designers’ and developers’ view. Component only refers to single component instead of composed components since component composition is consider as Function in the metamodel. One Function can be implemented by one or more Component, and different Functions can be implemented by one Component. ComponentInstance and Interface related to component have the same symentics as in UML [5]. FunctionalConstraint and NonfunctionalConstraint are the text description of functional and nonfunctional requirements of AplicationSystem, Function or Component. The vertical integration relationship among data layer and function layer is reflected by the consumption or production relationship between Data and BasicElement which may be ApplicationSystem, Function or Component.
Fig. 3. Metamodel at Data Layer
Fig. 4. Metamodel at Function Layer
A UML-based System Integration Modeling
95
3.3. Metamodel at Workflow Layer The main elements of workflow in SCS are Activity, DataPool, ControlFlow, ObjectFlow and RealtimeConstraint as presented in Fig. 5a. Activity: ExecuteActivity is a action which is executed by only one component instance. The detailed SignActivity and LogicActivity are showed in Fig. 1.5c. AndSplitActivity splits a control flow into multiple concurrent control flows. OrSplitActivity splits a control flow into multiple control flows, and only one of them can be executed. AndJoinActivity is used to join multiple control flow as one control flow synchronously. OrJoinActivity joins multiple control flow as one control flow without synchronization. DataPool: Data in workflow is generalized as ApplicationData related to the business and ControlData used to make decision at OrSplitActivity. DataPool is the element storing and managing one or more kinds of application data instances. ControlFlow: ControlFlow connects two activities with zero or more kinds of control data and condition used for decision making at OrSplitActivity. ObjectFlow: ObjectFlow from DataPool to ExecutionActivity can be divided into two categories represented in Fig. 1.5b: ConsumeFlow and ReferenceFlow. ComsumeFlow means the objects stored in DataPool are comsumed. ReferenceFlow means the objects are just be used. RealtimeConstraint: In SCS, some activities, control flows and application data instances have time constraint represented by the RealtimeConstraint element. Li [12] has concluded six kinds of time constraints: delay constraint, flow delay, limited duration, deadline, time distance constraint and fixed-date. The delay constraint is suitable for the time constraint of workflow in SCS. Some activities and control flows can’t be interrupted which is represented by the Interrupt attribute. The SCondiction attribution of ExecutionActivity means the start condition of the activity. The vertical integration relationship of data layer and workflow layer is reflected by the relationships between Data and DataPool, ControlFlow and ObjectFlow. The relationships among Workflow and ApplicationSystem, ExecuteActivity and ComponentInstance reflect the integration relationship of function layer and workflow layer.
b. ObjectFlow, ControlFlow and Data
a. main elements of workflow
c. SignActivity and LogicActivity
Fig. 5. Metamodel at Workflow Layer
96
F. Zhiqiang, G. Hui, S. Jufang and Z. Li
4. UML Based System Integration Modeling Language For the description of integration model and the communication of designers, a modeling language is needed. In this section system integration modeling language for application system design (SIML4ASD) based on the metamodel is defined by extending UML2.0. 4.1. SIML4ASD SIML4ASD reuses part of elements of UML2.0 with the <<merge>> relationship, and then extends some elements of UML using profile mechanism. SIML4ASD divides elements into three packages which are data, function and workflow. Data Package: The elements in data package are ApplicationData, ControlData, DataInstance, DataDomain, Instantiation, Generalization, Composition, Aggregation and Class Diagram, where, the first three are the element extended from UML and the others are the elements of UML. Function Package: ApplicationSystem, Function, FunctionalConstraint, NonfunctionalConstraint, Component, ComponentInstance, Interface, Association, Realization, InterfaceRealization, Dependency, Component Diagram, UseCase Diagram, Component Diagram and Sequence Diagram are in function package, where, the first four are extended from UML, the others are the elements of UML. Association is connection from ApplicaitionSystem to Function. Realization is connection from Component to Function. InterfaceRealization and Dependency connect Component to required and provided Interface separately. Besides this, fucntion package imports data package, which means the elements in data package are included in fucntion package. Thus the Instantiation in data package can be used to connect Component to ComponentInstance. Workflow package: the elements in workflow package are Workflow, ExecutionActivity, DataPool, ObjectFlow, ReferenceFlow, ConsumeFlow, ControlFlow, ExceptionFlow, OrSplitActivity, OrJoinActivity, AndJoinActivity, AndSplitActivity, InitialActivity and FinalActivity. All of these are extended from UML. Workflow package imports the function package. The extended elements of SIML4ASD are listed in Table 1.1. The relationships among Application System, Function, Component, and Data are expressed by CDataType and PDataType attributes. The relationship between DataInstance and ObjectFlow/ControlFlow are expressed by the DataType attribute. These three attributes use “;” to split the different DataType. The relationship of ExecutionActivity and ComponentInstance are expressed by the ExeCmpt attribute recording the component name. The SCondtion attribute recording activity name is used to express the start condition of ExectutionActivity. Time constraint is expressed by the four attributes: minimum duration (Tmin), maximum duration (Tmax), actual duration (Trun) and time unit (Unit). 4.2. Multi-view Modeling of SIML4ASD Integration model involves many elements. It is hard to describe all elements in one view. Due to the difference of people’s concerns with integration model, it is
A UML-based System Integration Modeling
97
better to describe the model in multiple views. SIML4ASD has three views base on UML diagrams: data view, function view and workflow view. The Data and the relationship between Data can be described in data view using the class diagram. Function view has five sub-views. Application system view is used to describe the application systems and data exchange between them using component diagram. Application system function view is used to describe the function of each system using “use case” diagram. Component View can be used to describe a component and its interface using component diagram. The interaction of components can be expressed via component interaction view using sequence diagram. The function to component view is to describe the relationship of function and component, i.e. which function is implemented by which components. Workflow View is used to describe workflows by activity diagram. Table 1.1. Stereotype of SIML4ASD Modeling Concept / Stereotype / UML Element DataDomain / ASD_DD / Package ControlData / ASD_CD / Class DataInstance / ASD_DI / ClassInstance ApplicationSystem / ASD_AS / Component Function / ASD_F / UseCase Component / ASD_C / Component FunctionalConstraint / ASD_FC / Constaint NonfunctionalConstraint / ASD_NFC / Constaint Workflow / ASD_WF / Activity ExecutionActivity / ASD_EA / Action InitialActivity / ASD_IA / InitialNode FinalActivity / ASD_FA / ActivityFinalNode AndJoinActivity / ASD_AJA / JoinNode OrJoinActivity / ASD_OJA / MergeNode AndSplitActivity / ASD_ASA / ForkNode OrSplitActivity / ASD_OSA / DecisionNode ControlFlow / ASD_CF / ControlFlow ExceptionFlow / ASD_EF / ControlFlow DataPool / ASD_DP / DataStoreNode ObjectFlow / ASD_OF / ObjectFlow ReferenceFlow / ASD_OFR / ObjectFlow
Extended attributes
CDataType:string PDataType:string
Tmin:double Tmax:double Trun:double Unit:enum
DataType:string
ConsumeFlow / ASD_OFC / ObjectFlow ApplicationData / ASD_AD / Class ExecutionActivity / ASD_EA / Action ControlFlow / ASD_CF / ControlFlow
ExeCmpt:string SCondition:string DataType:string
98
F. Zhiqiang, G. Hui, S. Jufang and Z. Li
5. Related Work Since system integration involves many areas, there is no such language that is sufficient to describe all elements involved in system integration. Balasubramanian [13] and Shetty [14] , researcher of Institute for Software Integrated Systems of Vanderbilt University, provided SIML by composing two kind of Domain Specific Modeling Language respectively. The SIMLs provided by Balasubramanian and Shetty are used to describe the integration model of two kind of systems developed in different language and style. The integration of application systems involves three layers, i.e. data layer, function layer and workflow layer. The modeling languages studying data, function and workflow have made following progress. Data modeling: the metamodel is the core of a language. Currently, the wellknown data metamodel are CORBA [15], DDS [16], EXPRESS [17] and IDEF1X [3] data metamodel. CORBA supports fewer data types, especially the collection type. DDS provides richer data types that are closer to user. The UML profile for DDS is also released by OMG. The data types supported by EXPRESS are less than DDS. IDEF1X is a data modeling language used to develop semantic data model. DDS supports the most of data types among the four. It is the main reference of the metamodel at data layer. But the latter is more detailed than the former. Function modeling: the main function modeling methods are Functional Flow Block Diagram (FFBD) [18], Hierarchical Input Process Output (HIPO)[19], N2 Chart[20], Structured Analysis and Design Technique (SADT)[21], IDEF0[2] and UML[5]. Function modeling for the application system integration of SCS is aimed at describing application system, function, component and the relationships among them. These function modeling languages, unlike UML, cannot describe the components. But the relationship between functions and components are not defined in UML. Workflow modeling: there are mainly six workflow modeling methods: 1) Activity network diagram based modeling method [22]; 2) Petri Net based modeling method [23]; 3) State Diagram based modeling method [24]; 4) dialog model based modeling method [25]; 5) UML activity diagram based modeling method [5]; 6) IDEF3 based modeling method [4]. The methods based on Petri Net, UML activity diagram and IDEF are the most representative of the six methods above. The first is commonly used for workflow simulation and analysis due to Petri Net theory, but it’s hard to learn and understand. The latter two are used widely for workflow modeling because they are easy to learn and understand. But UML activity diagram is better than IDEF3 in expansibility and that activity diagrams are a recognized form of modeling real time systems [26]. Since model describing is the primary purpose of SIML4ASD, the method based on UML activity diagram is chosen. According to the survey above, the UML and IDEF are suitable for the integration modeling. Zhou [27] has used UML to describe the system integration model. Xiao [28] has used IDEF to describe the business integration model. Since the component needs to be described in integration model at function layer and IDEF does not support the requirement well, hence, the UML based system integration modeling language is defined for application system design of SCS.
A UML-based System Integration Modeling
99
6. Conclusion When designing application systems of SCS, the data exchange, function assignment and workflow must be described clearly. However, currently, there is no such modeling language to serve the purpose. Therefore, a research about the SIML for application system design of SCS is studied in this paper. There are three contributions of this paper: 1) an integration framework of application systems of SCS is proposed, which consists of data, function and workflow; 2) the integration metamodel, explaining the data, application system, function, component, workflow and their relationship for the first time, is introduced based on the framework; 3) a UML based SIML is defined, which is easy to learn, use and understand for the system designer. This work is meaningful for two reasons: 1) as the integration metamodel is defined and a UML based SIML4ASD is provided, system designers can describe the integration model of application systems easily and clearly in multi-view, which is helpful for communication of designers; 2) systems are usually evaluated after their design, and automatic evaluation methods are more and more mature in recent years. A clear and unambiguous definition of integration metamodel and SIML4ASD is the basis of automatic system evaluation. This paper is supported by the National Natural Science Foundation of China under Grant No.60773155 and the National Grand Fundamental Research 973 Program of China under Grant No.2007CB310803.
7. References [1] [2] [3] [4] [5] [6] [7] [8]
Mei Jiao, “Development Features and Prospects of Shipborne Combat System at Home and Abroad”, Ship Command and Control System, vol. 5, July 1996, pp. 817.(in chinese) Draft Federal Information Processing Standards Publication 183. INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEF0). 1993 itl.nist.gov. Integration Definition for Information Modeling (IDEFIX). 21 Dec 1993. www.itl.nist.gov/fipspubs/idef1x.doc Richard J. Mayer et al. Information Integration for Concurrent Engineering (IICE): IDEF3 Process Description Capture Method Report. Logistics Research Division, Wright-Patterson AFB, OH 45433 OMG. OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2. http://www.omg.org/docs/formal/07-11-02.pdf Deng Su, Zhang Wei-Ming, Huang Hong-bin, Information System Integration Technology, 2nd ed., Publishing House of Electronics Industry: Beijing, 2004. (in chinese) Wang Hui-Bin, Wang Jin-Yin, Information System Integration and Fusion Technology and Its Application, National Defense Industry Press: Beijing, 2006, pp.21-75. (in chinese) Zhang Xiao-Juan, “System Integration in the Contemporary Business Information Systems-Framework,Implementation and Case Study”, 4th International Conference on Wireless Communications, Networking and Mobile Computing, Dalian. 2008. pp:1-6
100
F. Zhiqiang, G. Hui, S. Jufang and Z. Li
[9]
Edward A. Stohr, Jeffrey V. Nickerson, Enterprise Integration: Methods and Direction. Oxford University Press: New York, 2003, pp:227-251 Giachetti R.E., A Framework to Review the Information Integration of the Enterprise, International Journal of Production Research, 2004, Vol. 42, Iss. 6, pp.1147-1166. Workflow Management Coalition,The Workflow Reference Model-TC00-1003 v1.1. 1995. Li Hui-fang, Fan Yu-shun. "Overview on Managing Time in Workflow Systems", Journal of Software, vol 13(8), 2002, pp.1552-1558 (in chinese) Balasubramanian Krishnakumar, Schmidt Douglas C, Molnar Zoltan, Ledeczi Akos. Component-based System Integration via (Meta)Model Composi-tion. 14th Annual IEEE International Conference and Workshops on the Engineering of ComputerBased Systems, Tucson, AZ . 2007. pp: 93-102 Shetty S, Nordstrom S, Ahuja S, Di Yao, Bapty T, Neema S. Systems Integration of Large Scale Autonomic Systems using Multiple Domain Specific Modeling Languages. 12th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems, 2005. pp: 481-489 OMG. Common Object Request Broker Architecture - for embedded. http://www.omg.org/cgi-bin/doc?ptc/2006-05-01.pdf OMG. Data-Distribution Service for Real-Time Systems, V1.2. http://www.omg.org/cgi-bin/doc?formal/07-01-01.pdf ISO 10303-11:2004 Industrial automation systems and integration -- Product data representation and exchange -- Part 11: Description methods: The EXPRESS language reference manual Function model. http://en.wikipedia.org/wiki/Function_modeling#cite_note-11 Sandia National Laboratories. Sandia Software Guidelines Volume 5 Tools, Techniques,and Methodologies. 1992 .http://www.prod.sandia.gov/cgibin/techlib/access-control.pl/1985/852348.pdf NASA. Techniques of Functional Analysis. In: NASA Systems Engineering Handbook June 1995. p:142. John Mylopoulos. Conceptual Modelling III. Structured Analysis and Design Technique (SADT). Retrieved 21 Sep 2008. SADIQ S,ORLOWSKAM.On correctness issues in conceptual modeling of workflows[A].Proceedings of the 5th European Conference on Information Systems[C].Cork,Ireland:Cork Publishing Ltd,1997. W.M.P.van derAalst.TheApplication of Petri Nets to Workflow Management.The
[10] [11] [12] [13]
[14]
[15] [16] [17] [18] [19] [20] [21] [22] [23]
Journal of Circuits,Systems and Computers,1998,8(1):21~66. [24] Georgakopolous D,Hornick M,ShethA.An overview of workflow management:from process modeling to workflow automation infrastruc-ture[J].Distributed and Parallel Database,1995,3(2):119~152. [25] Leymann F,Altenhuber W.Managing business processes as an information resource[J].IBM Systems Journal,1994,33(2):326~348. [26] Chang E, Gautama E, Dillon T S. Extended activity diagrams for adaptive workflow modelling[C]// Fourth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing. Magdeburg, 2001: 413-419. [27] Yonghua Zhou, Yuliu Chen, Huapu Lu. UML-based Systems Integration Modeling Technique for the Design and Development of Intelligent Trans-portation Management System. IEEE International Conference on Systems, Man and Cybernetics. 2004. pp: 6061 - 6066 [28] Xiao Yan-Ling, Xu Fu-Yuan, Hu Wen-Bo. Business Process Reengineering Based on IDEF Methods. Proceedings of the 2004 IEEE International Conference on Information Reuse and Integration. 2004. pp: 265 – 270
Contribution to Interoperability of Executive Information Systems Focusing on Data Storage System Guillaume Vicien1, Yves Ducq1, Bruno Vallespir1 1
IMS UMR 5218 CNRS, Dept LAPS / GRAI Group, 351, cours de la Libération, 33405 Talence Cedex – France
Abstract. Nowadays, performance improvement in order to reach the economic, technical and social objectives has become essential for all enterprises whose want to stay competitive. For this reason, enterprises should set up an executive information system which will give them their performance’s level at every moment through different performance indicators. The developement of those systems is long and difficult and different ineroperability problems can occur especially during the design of the data storage system. Those interoperability problems disturb the system and the agregation of the different performance indicators.This article aims in a first part to propose a framework for the design and implementation of the data storage system. In a second, we analyse the different possible architecture and make their comparison. Keywords: executive information system, performance indicators, interoperability
1. Introduction Ever since Jonhson and Kaplan published in 1987 their seminal book entitled “Relevant Lost – The rise and fall of management accounting” [1], performance measurement gained increasing popularity both in practice in the enterprises and in research [2]. Today, the enterprises have understood that they need performance measurement and performance management practices in order to be competitive and increase their development. In fact, managers are continually measuring or requesting measures and management could hardly exist nowadays without measurement [3]. To measure their performance, enterprises have to define a performance indicators system that allows to verify the accomplishment of organizational objectives and to help the managers to take the best decisions. To define this system, many methodologies have been developped since many years like the Balanced Score Card [4], Prism method [5] or ECOGRAI [6].
102
G. Vicien, Y. Ducq, B. Vallespir
When all the performance indicators are defined, the enterprise has to set up an executive information system that will be able to restore the indicators on different forms (dash boards, OLAP analysis, data mining...). Executive information system uses different computing tools like ETL (Extract, Transform and Load) and Data warehouse to aggregate, store and restore the different performance indicators. The first applications of computing tools to help managers to take decisions appear at the beginning of the 90’s and the development of data warehousing and OLAP technologies date of the middle of the 90’s [7, 8]. Nowadays, the Business Intelligence market that includes all the different computing tools is very developed and still developing very quickly. This article aims to show the importance in the choice of the structure and the modelling use for the data storage system of an executive information system in order to aggregate the different performance indicators without interoperability problems. This paper is composed of two parts. The first one begins with the presentation of executive information systems in order to introduce the different interoperability problems that can be found in those systems. The second one focuses on the data storage process proposing a framework for their design and comparing the different possible architectures.
2. Executive Information Systems Nowadays, executive information systems are common place in all sectors of industry and commerce and in all sized enterprises. Indeed, we observe for few years an increasing interest of the small and medium sized enterprises for executive information systems due to the price decrease of computing applications. However, we do not found methodology for the implementation of performance indicators system within executive information systems and we notice several failures in enterprises [9, 10]. 2.1. Critical Success Factors of Executive Information Systems Executive information system development and implementation, which usually tales around 6 and 12 months [11] is a risky task due to the fact that many elements take part in this process and are closely llinked to one another. The riks that something goes wrong are very high [12]. A study realized by Poon [13] have showed that failures occure in 70% of cases and could lead to the reliquishment of the project. Furthermore, human ressources are highly involved in this kind of project and they will be very important in its success. Indeed, they will have many responsibilities including selecting hardware and software, identifying information requirements, locating and accessing needed information, designing screens ans providing training [14]. It exists in the literature many articles that deal with executive information system success factors and the works of Salmeron [11] have been selected. These research work propose to established three categories to study the success keys: human
Contribution to Interoperability of Executive Information Systems
103
resources, technical and information resources and system operation. The study results are proposed in the table 1 below. Table 1. Keys to EIS success [11] Human resources
User’s interest 96.55 %
Competent and balanced EIS staff 65.52%
Executive sponsor’s support 62.07%
Technical and Information resources
Right information needs 96.55%
Suitable Soft/Hard 68.96%
Others 10.34%
System operation
Flexible and sensitive system 79.31%
Speedy development of a prototype 48.28%
Others 16%
Others 6.9%
Regarding this table we can conclude that there are three main keys success for executive information system. The first one, “user’s interest” requires enterprises to involve their employees from the beginning of the system design. The second one, “right information needs” is obvious if an EIS intends to satisfy the manager’s needs of information. The third one, “flexible and sensitive system” is inherent to the concept of executive information system and the final users would like to use a complexe, integrated and interoperable system that will evolve easily with their new expectations. 2.2. Executive Information System Process and Architecture Futher to the different keys success, we are going to see more in details the process and the architecture of executive information systems. 2.2.1 Process The executive information system is composed of three sub-processes. The first process “Data recovery” consits in the recovery of the operational data stored in the different operational data sources of the enterprise. This process is also composed of three sub-processes, extraction, transformation and loading. Extraction means the process that extracts data from enterprise operational data sources using adapters. Those adapters consult metadata to determine which data to extract, how and when. Transformation is the process which transforms the extracted data into a consistent format applying rules defined in the metadata repository. This process is also responsible for data validation and data accuracy. The process of load is responsible for loading the transformed data into data warehouse using target data adapters. Those adapters also consult metadata [18]. The second process “Indicators aggregation and storage” consists in the data storage and their processings in order to aggregate the different performance indicators. The data storage will also allow the historical management of the indicators and facilitate the information access.
104
G. Vicien, Y. Ducq, B. Vallespir
Finally, the third process “indicators restitution” allows final users to recover performance indicators on different forms. The more common widespread restitution forms are dashboards, OLAP analysis and datamining. Those restitution forms have to be developed according the final users expectations. 2.2.2 Architecture The executive information system process is supported by a specfic architecture composed of different computing applications, figure 1.
Fig 1. Executive information system architecture
This architecture is composed of three main parts according to the executive information system process. The first one “recovery” is composed of the different operational data stores and the ETL (Extract, Transform and Load) which will operate the data transfer until the data warehouse. The “storage” is composed of different elements which allow the storage of the data and the different performance indicators. We will see later in the article that the storage system could be different according to the enterprise expectations and those different architectures will be analysed. The “restitution” architecture is developed according to the final users expectations. Indeed, many computing tools are on the market and are used to propose different restitution modes. 2.3. Interoperability in Executive Information Systems Due to complex architecture of executive information systems, different interoperability problems could occur. We propose the enterprise interoperability framework developped by Chen [16] and proposed in figure 2., to caracterise the interoperability problems considered in these research works.
Contribution to Interoperability of Executive Information Systems
105
Fig 2. Enterprise interoperability framework
The research works presented in this paper are focused on the data barrier which is the most important to solve in the implementation of the executive information system (grey part). We have identified four major interoperability problems. For each problem, we will detect which solution has to be set up in order to solve this problem and position it in the framework. Interoperability problem 1: Data transfer between operational data sources and data warehouse. Enterprises use nowadays various operational computing tools and the ETL has to be able to transfer data between those different applications. ETL that we found on the market own different adapters that allow data transfer. If a specific adapter does not exist, it is possible to develop it but it is preferable for the enterprise to choose it ETL according to its operational data sources in order to avoid the development. We found the same kind of problem between ETL and data warehouse. Based on the previous description, this interoperability problem is then positioned in the framework as Data, C, Federated. Interoperability problem 2: When the data recovery process in launched, the ETL has to know which data does it have to recover? Where? When? Which processings have to be done? And Where the data has to be store? During recovery process design, it is necessary to specify all information about the operations which have to be realized on the data. To do so, it is necessary to develop a metadata repository where all those information will be stored. Furthermore, the setting of a metadata repository makes the system evolution easier because the possible evolutions will be recording directly in the metadata repository. This interoperability problem is positioned in the framework as Data, Conceptual, Unified. Interoperability problem 3: Data that have to be stored in the data warehouse come from different and heterogeneous operational data sources and semantic interoperability problems will certainly appear in the data warehouse. So it is necessary to define and adopt a common semantic for all the data that have to be stored in the data warehouse. This standardization of the data will be supported by a metadata repository. The interoperability problem is positioned in the framework as Data, Conceptual, Unified.
106
G. Vicien, Y. Ducq, B. Vallespir
Interoperability problem 4: the setting up of OLAP analysis forces the designer to use a particular modelling. Indeed, OLAP analysis require a snow flake modelling of the data. The data will be stored in two different kinds of tables: fact and dimension. The interoperability problem is classified in the framework as Data, Conceptual, Unified. In conclusion, we realize that most of interoperability problems that occur in executive information system can be solved using a unified approach. This result is consistent allowing that the goal of an executive information system is to centralize data extracted from various and heterogeneous data sources. Furthermore, all those interoperability problems could be identified and solved during the process design in order to avoid system failure.
3. Storage System In the previous section are presented interoperability problems in executive information system and in this section we are going to present our contribution on the data storage system. This section is composed of three parts. In a first time, we propose a framework for the setting up of the storage system. In a second part, we choose the architecture of the storage system which allows to avoid interoperability problems. Finally, in the third part, we propose a formalism in order to model the different elements of the architecture. 3.1. A Five Stage Framework It exits in the literature many articles that proposed a framework for the building of storage system [17, 18]. We propose to use a five stages framework. 3.1.1 Stage 1 – Business requirements The first stage consists in the recovery of the different requirements of the system final users. This part is one for the most important as mentionned in section 2.1. This step is generally realized thanks to interviews of the system final users and all information could be stored in specification sheet. It is necessary to make a specification sheet for each performance indicator. It allows to centralize information and find it easily. 3.1.2 Data sourcing When all information are recovered, it is necessary to be sure that all the data necessary to aggregate performance indicators are available and identify the different processings to make on data in order to store them in the data warehouse. In order to model the data recovery process, we suggest to use the model proposed in our previous works [19]. 3.1.3 Target architecture The choice of the architecture is very important and we found in the litterature different architectures. This step will be detailled in the next section.
Contribution to Interoperability of Executive Information Systems
107
3.1.4 Tool selection When the architecture is defined, designers have to chose the different tools which will compose the architecture. It will depend of the chosen architecture and final users requirements. Indeed, designers have to answer users requirements ensuring that chosen architecture will support the different computing applications. 3.1.5 Administration One of the commonly neglected issues is the administration of the data warehouse after its implementation. The appropriate technical resources mustbe assigned to monitor query load and performance, to handle dynamic changes to the data structures, and to ensure platform scalability with increased user demands. Generally, data warehousing projects use the prototype approach to development and the success of the prototype will determine the overall success of the project. 3.2. Data Storage Architecture The data warehousing architectures provides discussions and examples of a variety of architectures [20]. We found in the litterature four main architectures : independent data marts, data mart bus architecture with linked dimensional data marts, hub and spoke and centralized data warehouse. The hub and spoke architecture is considered as the most complete and we have chosen to use this architecture. This architecture will be detailled below. With this architecture, attention is focused on building a scalable and maintainable infrastructure. Data are stored in two different databases, the data warehouse and the data marts. The data warehouse stored all operational data extracted from data sources which are necessary for the aggregation of the different performance indicators. Dependant data marts are developed for departmental, functional area or specific purposes (e.g., data mining).In the data marts are only stored all the performance indicators and some atomic data for specific analysis (e.g., OLAP analysis). Data marts independence improves the rapidity of the system and furthermore it allows it to be more easily scalable and maintainable. However, this architecture owns two disadvantages. The first one is the cost of this system which is more expensive due to the data quantity to store which is more important. The second one is the difficulty of development. Indeed, two different modelling have to be used, one for the data warehouse and one for the data marts. When the architecture is chosen, it is necessary to realize the modelling of the data warehouse and the data marts. 3.3. Data Storage System Modelling As explained in the previous section, the data warehouse and the data marts have different objectives and so it is necessary to use a specific modelling for each one.
108
G. Vicien, Y. Ducq, B. Vallespir
3.3.1. Data warehouse modelling The goal of the data warehouse is to centralize all operational data extracted from the different data sources. The fist step of the data warehouse building is the creation of the metadata repository. The metadata repository will allow to solve the interoperability problem 3 definied in section 2.3 about the heterogeneous of the data. Designers have to develop a common format for data storage. This common format has to be develop according to the different information recovered about data in order to limit the number of processinds which have to be done on data during the extraction process. Then, it is necessary to model the data storage using the 3rd normal form of relational databases. The main interest of the 3rd normal form is to avoid data redundancy. The modelling is composed of two parts. The first allows consits in the definition of the different tables and the relations between the tables. This modelling has to be done using entity relation model. 3.3.2 Data marts modelling The modelling of the data marts is very important in order to avoid the interoperability problem 4 about the need for specific analysis or applications (e.g. OLAP analysis) to use a specific modelling. It is so important to have well defined the users requirements during the first stage of the framework. In order to allow the aggregation of the different performance indicators and give the final users the access to detailed data, it is necessary to organize the data in a star schema. Star schema is composed of two kings of tables and we have defined a formalism in order to model the different elements of the star schema. Fact tables allow to store the different measures of the fact and are composed of different elements: (1) Fact name, (2) Key name, (3) List of entry in dimensions and (4) Specific attributes of the fact. The fact table formalism is: Fact_name [(F), (Fact_Key), (Entries), (Dimensions)] Dimensions tables allow to do analysis of the fact according to the dimension and are also composed of different elements: (1) Dimension name, (2) Key name, (3) List of the different members of the dimension, for example the dimension Time could have for members: year, month, week and day, (4) Specific attributes of the dimension. The dimension table formalism is: Dimension_name [(D), (Dimension_key), (Members), (Attributes)] In order to illustrate the formalism, we are going to take the example of the performance indicator: number of stock shortages per item and product. Fact table: Stock_Shortages [(F), (Key_Stock_Shortage), (Key_Item, Key_Product, Key_Time), (Causes)]. Dimension tables: Items [(D), (Key_Item), (Item_Number), (Item_ Name)] Product [(D), (Key_Product), (Product_number), (Product_name)] Time [(D), (Key_Time), (Day, Week, Month, Year), ()] The figure 3 illustrates the star schema of the example.
Contribution to Interoperability of Executive Information Systems
109
Fig 3. Example of star schema
When all the star schema are finished for all the performance indicators which have to be agregated, it is necessary to find the different common dimensions in order to build the complete model of each data marts. The figure 4 shows a global star schema after the grooping of dimensions.
Figure 4. Global star schema
4. Conclusion This paper has allow to identify the different interoperability problems which can occur during the design of the data storage system of an executive information system. Thanks to their positionnement in the interoperability framework, the designers can identify them quickly and propose a solution. In the second part of this paper, the framework proposed for the data storage system permits to well identify the different steps of the design and the implementation of the system in order to assure the system success. Then, we have chosen to use the hub and spoke architecture and proposed a formalism to build the data storage elements model. Our future works, we will devoted on the restitution process and more particularly on the dashboards design. It will be interesting to design the dashboards using different concepts like decision centers or the coherence analysis developed by [21] in his previous works. Finally, we will have to apply those different results to a real case in order to verify their contributions and to adjust them according to the obtaining results.
110
G. Vicien, Y. Ducq, B. Vallespir
5. References [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21]
Johnson H. T., Kaplan R. S. (1987), Relevance Lost – The Rise and Fall of Management accounting, Harvard Business School Press, Boston, MA. Bittici U., Garengo P., Dörfler V., Nudurupati S. (2009), Performance measurement: Questions for Tomorrow, APMS 2009 conference, Bordeaux, France. Lebas M. J. (1995), Performance measurement and performance management, Production Economics, Volume 41, pp. 23-35. Kaplan R. S., Norton D. P. (1996), The balanced scorecard, Harvard Business Press. Neely A., Adams C., Kennerley M. (2002), The performance prism, Prentice Hall. Bitton M. (1990), ECOGRAI : Méthode de conception et d’implantation de systèmes de mesure de performance pour organisations industrielles, Thèse de doctorat, Université Bordeaux 1. Haouet C. (2008), Informatique décisionnelle et management de la performance de l’entreprise, Cahier de recherche numéro 2008-01. Cody W. F., Kreulen J. T., Krishna V., Spangler W. S. (2002), The integration of business intelligence and knowledge management, IBM Systems journal, Volume 41, Number 4, pp 697-713. Nord J., Nord G. (1995), Executive information system: a study and comparative analysis, Information & Management, Volume 29, pp. 95-106. Rainer R. K., Watson H. J. (1995), The keys to executive information system success; Journal of Management Information Systems, Volume 12, pp. 83-98. Salmeron J. L. (2003), EIS success: keys and difficulties in major companies, Technovation, Volume 23, pp. 35-38. Rainer R. K., Watson H. J. (1995), The keys to executive information systems success, Journal of Management Information Systems, Volume 84. Poon P., Wagner C. (2001), Critical success factors revisited: success and failures cases of information systems for senior executive, Decision Support Systems, Volume 30, pp. 393-418. Watson H. J., Aronson J. E., Hamilton R. H., Iyer L., Nagasundaram M., Nemati H., Suleiman J. (1996a), Assessing EIS benefits: a survey of current practices, Journal of Information Technology Management. Zode M. (2007), The evolution of ETL, from hand-coded ETL to tool-based ETL, Cognizant Technology Solutions. Chen D. (2009), Framework for enterprise interoperability, CIGI 2009 Conference, Bagnères de Bigorre, France. Murtaza A. H. (1998), A Framework for Developing Enterprise Data Warehouses, Information Systems Management, Volume 15, pp. 21-26. Mollard D. (2006), Systèmes décisionnels et pilotage de la performance, Lavoisier. Vicien G., Ducq Y., Vallespir B. (2009), Contribution to Interoperability of Decision Support Systems focusing on the data recovery process, IESA 2009 Conference, Pékin, China. Watson H. J., Ariyachandra T. (2005), Data Warehouse Architectures: Factors in the Selection Decision and the Success of the Architectures, Report available on http://www.terry.uga.edu/~hwatson/DW_Architecture_Report.pdf. Ducq Y. (1999), Contribution à une méthodologie d’analyse de la cohérence des systèmes de production dans le cadre du modèle GRAI, Thèse de doctorat, Université Bordeaux 1.
GRAI-ICE Model Driven Interoperability Architecture for Developing Interoperable ESA Lanshun Nie1, Xiaofei Xu1, David Chen2, Gregory Zacharewicz2, Dechen Zhan1 1 2
School of Computer Science and Technology, Harbin Institute of Technology, 150001 Harbin, China. IMS/LAPS/GRAI, University Bordeaux 1, 351 Cours de la Liberation, 33405 Talence Cedex, France.
Abstract. This paper presents GRAI-ICE Model Driven Interoperability Architecture (MDI) which is developed based on MDA (Model Driven Architecture) of OMG and some initial works performed in INTEROP NoE. This MDI architecture aims at supporting the development of changeable on-demand and interoperable ESA (Enterprise Software Application). The architecture defined five modelling levels, i.e., Top CIM, Bottom CIM, Object oriented PIM, Pattern oriented PSM, and Component and configuration oriented CODE. This paper presents in detail core concepts and rational of each modeling level. An application example in nuclear equipment industry is outlined. Keywords: MDI, MDA, ESA, Interoperability, Architecture, Model transformation
1. Introduction Today, with the increasing pressure from competitive market, enterprises particularly SMEs are obliged to work in network in order to meet the changeable and customized demand. ESA (Enterprise Software Application) supporting the business should be adaptable and flexible to the business change. In such networking approach and with the development of the globalization of the economy, enterprises have to cooperate with partners such as material suppliers, service suppliers, distributor, retailer and public administration to provide highquality products and services to customers. In order to cooperate, it is required for enterprises to have capabilities of interoperability in the level of both business and IT/software systems, i.e. ESA. Changeable on-demand and interoperable ESA brings great challenge to software architecture, implementation, deployment, in a word, software development [1, 2]. This paper demontrates how MDI (Model Driven Interoperability) contribute to these developments.
112
L. S. Nie, X. F. Xu, D. Chen, G. Zacharewicz and D. C. Zhan
1.1. Problems and Research Objectives Code is the core artefact in traditional software development process. This process is usually very long, and the cost is usually very high. It is not rapid and adaptative enough to develop changeable on-demand interoperable ESA. Since years there is a shift from code-based software development to model-based software development. The most known approach is MDA (Model Driven Architecture)[3]. In the objective of tackling interoperability at each level of life cycle development, MDI (Model Driven Interoperability) architecture has been introduced by generalysing the steps of MDA. It deals with interoperabilty between ESAs during their respective developments. In this new methodology, conceptual models of enterprise interoperabilty are elaborated to facilitate the interoperablity at the coding level. Software development starts from business level where a Computing Independent Model (CIM) is elaborated and then transformed into executable ESA system by automatic/semi-automatic transformation and code generation tools. There are still some research questions due to the fact that MDA, and by heritage, MDI only defines the framework and some guiding rules, but not detailed method to follow, nor modelling languages. For example enterprise modelling techniques are not well considered at the CIM level. Should the CIM level be further divided in order to model both business and software requirements? The interoperability among adjacent levels is also not sufficiently studied. The research objective is to address the problems mentioned above through the elaboration of a Model Driven Interoperability Architecture (entitled GRAI-ICE MDI) taking into account the MDA and some initial works performed in INTEROP NoE. This MDI architecture aims at defining both the modelling levels of the architecture and model transformation method between adjacent levels. The proposed GRAI-ICE MDI will support the development of interoperable, configurable and executable next generation ESA. 1.2. Background and Related Works Model Driven Interoperability (MDI) architecture [2, 3] aims at decreasing the complexity and difficulty of interoperable software system development by decomposing complex, abstract system into multiple levels. The basic ideas are: (1) decoupling the requirement specification and function specification from implementation specification in specific platform; (2) establishing computation independent model (CIM) which describes business requirement, platform independent model (PIM) which describes design of software, and platform specific model (PSM) which describes implementation mechanism of system; (3) transformation and mapping from upper level model to lower level model, refining the model and automatically generating software from models [4,5]. It has been recommended for modelling using languages and technologies such as UML, MOF and CWM, and transforming models using technologies such as meta-model and pattern [6, 7]. However, MDI only defined some guiding rules, but not the details such as concrete modeling elements, modeling methodology and model transformation method [8]. Consequently, it is necessary to select or refine modeling method(s) and organize them consistently.
GRAI-ICE Model Driven Interoperability Architecture for Developing Interoperable
113
Researchers have studied some most known existing modeling methodology, language and tools such as CIMOSA [9], GRAI [10] and IDEF[11]. UML (Unified Modeling Language) is the most widely used modeling language for software specification [11]. The former is suitable for business level, i.e. CIM level. The latter is suitable for software oriented modelling, i.e. PIM and PSM levels. However, there still exists a big semantic gap between them and no existing approach shows how to integrate them to a consistent architecture. Therefore, the question is still open on how to select, from the existing business modeling methods and software modeling methods, adequate formalisms, to refine, combine and integrate them into MDI architecture. Motivated by the requirement of developing changeable on-demand and interoperable ESA, and based on some existing modeling languages, a Model Driven Interoperability architecture, entitled GRAI-ICE MDI architecture, is proposed. GRAI refers to GRAI methodology and is used at CIM level to describe business user oriented requirements. ICE means Interoperable Configurable and Executable. This approach is based on some initial works performed in INTEROPNoE and further developed within the frame of INTEROP VLab through a research collaboration between University Bordeaux 1 (IMS/LAPS) and Harbin Institute of Technology (HIT) and also the company GFI.. It aims at defining concrete modelling elements (concepts) and relations among them at all levels of MDI architecture so that the model of ESA can be described precisely and consistently by these elements. This architecture supports model transformation top-down (CIM→PIM→PSM→CODE), and from code to system deployment. Also performed in INTEROP NoE, R. Grangel etc. proposed a similar MDI framework. They broke down CIM level into two sublevels, i.e. top-level CIM and bottom-level CIM. Besides this, their research work focus on transformation from top-level CIM model to bottom-level CIM model, with an example of transforming GRAI extended actigrams into UML activity diagrams[12,13]. 1.3. Purpose and Structure of the Paper The purpose of the paper is to present the preliminary research results on Model Driven Interoperability architecture for developing Interoperable ESA. In this paper focus is on the set of modelling methods and languages defined in MDI. The related transformation methods will be presented in a forthecoming paper. After the introduction given in section 1, the global GRAI-ICE MDI architecture is presented and explained in section 2. Then, section 3 to section 5 will explain the problems, target of modelling, core concepts and relations, as well as modelling methods used at the three main levels (CIM, PIM, and PSM). Section 6 presents the last level of the architecture (ESA component and system level) and outlines the principle of model transformation and supporting tools. An application case is discussed in section 7. Finally section 8 and 9 respectively conclude the paper and discuss on future perspectives.
114
L. S. Nie, X. F. Xu, D. Chen, G. Zacharewicz and D. C. Zhan
2. Overview of GRAI-ICE MDI Architecture GRAI-ICE MDI follows the basic structure of MDA proposed by OMG. It includes four modelling levels and one system level. It also includes transformation methods between these levels. The global view of GRAI-ICE MDI architecture is shown Fig.1. Note that CIM level is divided into two sub-levels: Top CIM (business oriented CIM) and Bottom CIM (ESA oriented CIM). Business Oriented CIM (GRAI*)
Decision Oriented
Business-oriented CIM Global Model Dec
Phy
Inf
AS-IS
Func
Org TO-BE 1
Models
ESA Oriented CIM For inter-op
TO-BE 2
Transform: Business CIM→ ESA CIM
Transform.
Process Oriented
ESA-oriented CIM Global Model GRAI ESA Decision Model
Function/Process View
UML+
Information View
GRAI TO-BE ESA
Organization View
ESA Model
Views Transform: CIM→ PIM
Transform.
ICE-PIM
Object Oriented
For inter-op
UML+
Transform: PI M→ PSM
Transform.
ICE-PSM For inter-op
Pattern Oriented
Static Confi. Model BC Model
XML+
Generator/Transform.
ESAComponent & System
Patterns Elements
EWF Model
ESA Implementation
Data Model (DB Schema)
Pattern based on framework Generator: PSM→ Code
Component & Configuration Oriented
Transf: PSM→ Confi.file
BC
Sys. Confi.
CC
Framework
Code/Conf. DB Table/View Generator/Transform.
Data Model (IDEF1X or E-R)
Role Model
Diagrams
Data Model (BO-R Model)
BO-Based Workflow Model
BO Model
Generator: PSM→ DB
EWF Confi..
DB Table/View
WF engi.
Platform(J2EE) Transform: CI M/PIM/PSM→ ESA Implementation ESA Implementation Specification ESA Manual
ESA Training
Global picture of GRAI-ICE Version: 1 (26-07-2006)
Fig. 1. GRAI-ICE MDI architecture
Top CIM, which is business oriented and based on GRAI methodology, is a set of models focusing on the description of decision making process, business process and physical product flow process. Bottom CIM, which is ESA oriented, extracts from Top CIM and describes more in detail business requirements which must be supported by ESA, i.e. function/process, information, organization and decision making structure. ICE-PIM is concerned with the object-oriented design of ESA. It focuses on identifying and describing business objects (BO). It includes BO model, BO-Based workflow model, role model, and data model.
GRAI-ICE Model Driven Interoperability Architecture for Developing Interoperable
115
ICE-PSM, which describes the implementation of ESA, is pattern oriented and XML based. It includes business component (BC) model, static configuration model, executable workflow model and relational data model. ESA system is assembled by business components. It provides service to users by parsing the executable workflow model and scheduling function of business components supported by workflow engine.
3. TOP CIM and Bottom CIM There are two main modelling objectives at CIM level. On the one hand, CIM supports business process modeling, analysis, and optimization, with business people as the stakeholder. On the other hand, CIM also supports the modeling of ESA requirements, with business people and software developer as the stakeholders. Consequently the CIM level of GRAI-ICE MDI is further divided in two sub-levels: Top CIM (business oriented) and Bottom CIM (ESA oriented). Business oriented CIM aims at modeling three kinds of process (or flow). The first is physical process and physical product flow, which supports the analysis and optimization of the time, cost, quality and needed services. The second is business process and document flow, which supports managing, controlling and recording physical process. The third is decision process and order/plan flow which aims at controlling and coordinating physical process and resources. Besides, it is also necessary to describe enterprise organization and decision-making structure. The core modeling concepts/elements of business oriented CIM are: (1) Physical Product, (2) Information, (3) Function/Action, (4) Resource/Facility, (5) Organization, (6) QQV (Quality-Quantity-Value points): the point or the location where input, output or support should be measured, verified, recorded, controlled, processed, or reported, (7) Connection Sign. The models at business oriented CIM level are composed by these elements and their relations. The meta-model of business oriented CIM is shown Fig. 2.
Fig. 2. Metamodel of business oriented CIM
All elements can be further classified into sub-elements. For example, the element “Function/Action” is classified into “function”, “business action”, “decision action” and “physical action”. The element “Information” is classified into
116
L. S. Nie, X. F. Xu, D. Chen, G. Zacharewicz and D. C. Zhan
“document”, “order”, “event” and “report”. The view of CIM model can be exactly described by the combination of these elements and sub-class of them. GRAI-ICE CIM model is composed of three kinds of process diagram and some UML class diagram for information, organization, resource, etc. Physical process model describes the transformation and state transition of physical product in manufacturing. It includes six kinds of basic elements, i.e. product, action, order, resource, organization and QQV. Business process controlling/recording physical process describes the transformation and state transition of documents, such as receipts, orders, reports. It includes four kinds of basic elements, i.e. information/documents, order, action, and organization. Decision process model is based on GRID model of GRAI methodology. It has two dimensions. One is the decision level, for example strategic, tactics, operational levels. The other is the functions. The decision process model describes both the decision making process and the results which coordinate various functions and control other decision making processes. Information entities and the relations can be identified by analyzing the information flow embedded in business process to build information model. Also, organization model is also needed to construct at this level. Relation inside each kind of elements, such as information, organization, function, product, and resource, is described using UML class diagram. Analysis and simulation can be performed on business oriented CIM (AS-IS) of existing system. Then, by optimization and re-engineering, the TO-BE CIM can be obtained Business requirement for ESA is analyzed on the basis of TO-BE CIM. The result is ESA oriented CIM which focus on software requirement definition. For example, the physical process is not concerned since ESA does not control this process directly. We refine models extracted from TO-BE CIM and distinguish those activities (processes and information) which will be processed by machine or human with human-machine interaction. Due to the limited space, the specification of ESA oriented CIM is not described in detail in this paper.
4. ICE-PIM ICE-PIM is based on object-oriented approach, UML and workflow technology. The core concept BO is proposed for integrating both the process oriented model and object oriented software implementation. ICE-PIM is the bridge connecting business model and software implementation. At this level, information entities in the business process of CIM are abstracted and formalized as Business Objects (BO) describing the data structure, data dependency and relations. From the perspective of users, BO is an information entity with its state transitions and operations. From the perspective of software implementation, BO is an integrated object with unique identity, a lifecycle, several data sets and several operation sets. For example, the abstraction of a purchasing order is a BO. It provides a good basis for component-based software development. As mentioned above, CIM is more process oriented, in addition to
GRAI-ICE Model Driven Interoperability Architecture for Developing Interoperable
117
BO, it is necessary to transform business process of CIM into workflow model. In other words, PIM mainly consists of business objects model and workflow model. The meta-model of ICE-PIM is shown in Fig. 3.
Fig. 3. Metamodel of GRAI-ICE PIM model
Based on the meta-model, the composition of PIM model is as following. Business object model describes BOs and relationship of BOs. BO integrated diagram describes the detail of BO in four dimensions. (1) BO Data diagram describes the relations among data sets in IDEF1x. (2) BO class diagram describes the DPR (controlling relation between operation and data set), the relations among OP (operation of BO) and activity AT (activity set of BO). (3) BO state diagram describes the state SS, transition ST, and the properties associated with lifecycle. (4) BO use case diagram describes the relation among roles and operations. Relations among several BOs are described by BO-R model in two levels. The first level, i.e. BO level, describes the data dependency relations among BOs, such as association and integration. The second level, i.e. entity-relation level, considers the data set inside BO as entity and then describes the relations among them. Workflow model describes the sequence of activities of one BO of multiple BOs. The business object model is the core of PIM level. Workflow model assembles BOs into process supporting business function. Data, operation and state of BO provide input, output and trigger event for workflow exectuion. Data model describes the data schema of all BOs and provides global business view for users.
118
L. S. Nie, X. F. Xu, D. Chen, G. Zacharewicz and D. C. Zhan
Role model defines the access to data and operation. ICE-PIM provides all essential design facets of ESA.
5. ICE-PSM On one hand, ICE-PSM follows and inherents the design information from ICEPIM level models and transforms them into platform specific implementation model. On the other hand, it is the basis for code generation. Software pattern and platform specification are two cornerstones for ICE-PSM. Business Component (BC) is a largest grained unit of software development, and is a realization body of Business Object (BO) which is the finest grained operation unit of business system. BC is an implementation and running pattern for business components and is the core modeling elements in ICE-PSM. It is based on software pattern and XML, and can be transformed to code by code generator. It is a link between business object model and ESA system. Because of limited space, meta-model of BC is omitted. The executable workflow model consists of workflow model of PIM level and implementation details based on schedule pattern. It is described by the language supported by workflow engine (e.g. business process modelling engine, state transition event driven engine…). The static configurable model (SCM) is extracted from the relation between business object and role model. Pattern based ICE-PSM formulizes the software implementation model, simplifies the development of complex ESA and supports industrialized component development. The use of XML provides standard data source for code generation, automatic system configuration and deployment, and interoperability.
6. Generation of Code: ESA Components and System In this level, PSM will be transformed into business components and ESA system. There are three phases for business component. The first is stem business component in software development phase. The properties related with roles and individuals are still in parameter. The second is reused business component in deployment phase. Variable properties of BC are finalized for special role/user. So, the BC in this state is role-related component. The third is individualized business component in running phase. The components show different interfaces and behaviors according to the configuration and requirement of users. By doing so, the requirement of flexibility is distributed in several phases and the difficulty of development is decreased. The ESA development is based on business components. Firstly, the business component models are transformed into stem business components by code generator. Then, they are assembled by workflow, association mechanism and extend mechanism into complete business process. The workflow engine will manage the execution by invoking the different implement BO in the right order. Verification of correctness can be done by running simulation using the workflow
GRAI-ICE Model Driven Interoperability Architecture for Developing Interoperable
119
engine before execution. After that, they are configured and deployed based on the information of PSM.
7. An Application: Purchase Management The proposed architecture, methods, and associated tools and framework have been applied in ESA (Enterprise Resource Planning system) development in several Chinese enterprises. The time of development and deployment is shortened in more than 40%. The application in one of them, i.e. SHANDONG Nuclear Equipment Co. LTD, China is outlined below. Based on the GRAI-ICE MDI architecture, a set of tools have been developed. Firstly, a MOF, XML and Eclipse based extendable modeling tool supports defining modeling elements on demand and is used in modelling. A running framework has also been developed with a workflow engine inside for ESA. Some patterns in ESA have been extracted and formulized for business objects. XML and pattern based PSM model for BO is built. Based on pattern based PSM, we developed a PSM modeling tool and code generation tool, which support software developer for modeling PSM quickly, generate BC code, configure them and deploy them into the running framework. Fig. 4 (a) gives a segment of business process model at Top CIM level in purchase management domain. Fig. 4 (b) shows the BO-relation model at PIM level in the same domain.
Fig. 4. Example of CIM model and PIM model in purchase management domain
Fig. 5 (a) shows a segment of XML file, which is the PSM of purchase order BO. Fig. 5 (b) shows the running component of purchase order, which is generated from PSM model.
120
L. S. Nie, X. F. Xu, D. Chen, G. Zacharewicz and D. C. Zhan
Fig. 5. Example of PSM model and component of purchase order BO
8. Conclusions Changeability on-demand and interoperability are critical characteristics for ESA in today dynamical economical environment. A concrete and operable model driven interoperability architecture entitled GRAI-ICE MDI is proposed for developing ESA. It integrates both business modeling methods and software modeling methods, defines proper levels and transformation between models elaborated at these levels. The vertical transformation is developed straightforward along the thread “information entity→business object→business component model→stem business component→reused business component”. Dynamic component/service assembly based on workflow technology and variable business component gives good support to ESA assembly, configuration and deployment. The originality of the proposed approach is as following: (1) A nearly complete implementation of MDA/MDI is given in GRAI-ICE MDI, which appropriately integrates enterprise modelling, software modelling and software architecture. (2) The proposed architecture is interoperable, configurable and executable. (3) CIM is divided into business oriented CIM and ESA oriented CIM to capture both business and software requirements. (4) The proposed architecture and associated tools have been successfully applied in changeable on-demand and interoperable ESA development. Last but not least, the time of development and deploy has been greatly shortened.
9. Perspectives Considering the technical trend such as service computing and SaaS (Software as a Service), the GRAI-ICE MDI architecture should be adapted to service-oriented model-driven interoperable architecture. Business components will evolve to service components and ESA will evolve to service components composition.
GRAI-ICE Model Driven Interoperability Architecture for Developing Interoperable
121
More and more components and services are available on Internet. In order to incorporate, manage and reuse them in GRAI-ICE MDI architecture, it should not only be top-down, i.e. transformation and generation from business to IT, but also bottom-up, i.e. discovery, assembly and composition from existing IT elements to meet new business interoperability requirement[14]. Also, validation of the models by simulation can be envisaged. For now, GRAI-ICE MDI architecture focuses more on function requirement of ESA. However, non-function requirements such as confidentiality, security, timing, are crucial for run-time system. So, how to extend the proposed architecture to modeling non-function requirement and transform them into ESA is another important issue to consider in the future.
10. References [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]
[13] [14]
C Pautasso, T Heinis, G Alonso. Autonomic resource provisioning for software business processes. Information and Software Technology, 49(1): 65-80(2007) J.P. Bourey, R. Grangel, G. Doumeingts and A.J. Berre, “Report on Model Driven Interoperability”, Deliverable DTG2.3, INTEROP NoE, , April 2007, pp. 91 OMG. MDA guide version 1.0.1. http://www.omg.com/.12th June 2003 J. Bezivin, O. Gerbe. Towards a precise definition of the OMG/MDA Framework. Automated Software Engineering.(ASE 2001). Proceedings. 16th Annual International Conference on 26-29 Nov. 2001:273 - 280 T. Meservy, K. D. Fenstermacher. Transforming software development: An MDA road map. Computer, 38(9): 52-58(2005) J. Bezivin. From object composition to model transformation with the MDA. Proceedings of the 39th International Conference and Exhibition on Technology of Object-Oriented Languages and Systems, Santa Barbara, August 350 (2001) R. Lemesle. Transformation rules base on meta- modeling. Enterprise Distributed Object Com- puting Workshop. EDOC'98. Proceedings. Second International,3-5 Nov. 113 – 122(1998) W. Tan, L. Ma, J. Li, Z. Xiao. Application MDA in a conception design environment. First International Multi-Symposiums on Computer and Computational Sciences, IMSCCS'06: 702-704(2006) K. Kosanke. CIMOSA--overview and status. Computers in Industry, 101-109(1995) D. Chen, B. Vallespir and G. Doumeingts. GRAI integrated methodology and its mapping onto generic enterprise reference architecture and methodology. Computers in Industry, 387-194(1997) D. Chen, G. Doumeingts, F. Vernadat. Architectures for Enterprise Integration and Interoperability: Past, Present and Future. International Journal of Computers In Industry, 59(5), May 2008. R. Grangel, R. Ben Salem, J. P. Bourey, N. Daclin, Y. Ducq. Transforming GRAI extended actigrams into UML activity diagrams: a first step to Model Driven Interoperability, I-ESA 2007, Funchal (Madeira Island), Portugal, March 28– 30, 2007. R. Grangel, R. Chalmeta, C. Campos, R. Sommar, J. P. Bourey. A proposal for goal modelling using a UML profile. I-ESA 2008, Berlin, Germany, March 26–28, 2008. G. Zacharewicz, D. Chen; B. Vallespir. Short-Lived Ontology Approach for Agent/HLA Federated Enterprise Interoperability, I-ESA China 2009, Beijing, 22-23 April 2009.
Model for Trans-sector Digital Interoperability António Madureira1, Frank den Hartog2, Eduardo Silva3 and Nico Baken1,4 1 2 3 4
Network Architectures and Services (NAS) group, Delft University of Technology, Delft, The Netherlands TNO, Delft, The Netherlands Centre for Telematics and Information Technology (CTIT), University of Twente, Enschede, The Netherlands Corporate Strategy and Innovation department, Royal KPN, The Hague, The Netherlands
Abstract. Interoperability refers to the ability of two or more systems or components to exchange information and to use the information that has been exchanged. The importance of interoperability has grown together with the adoption of Digital Information Networks (DINs). DINs refer to information networks supported by telecommunication infrastructures and terminated by microprocessors. With an upcoming interest in services science and transsector business models, a stronger driver arises to further break the interoperability barriers across sectors. In this paper, we propose a novel model to address trans-sector digital interoperability, which by definition involves interoperability across different economic sectors connected by DINs. Particularly, we specify how a well known interoperability framework, the ATHENA framework, should be adapted for the economic sector plane. Based on data from the Eurostat survey on ICT usage and e-Commerce in enterprises, we illustrate how conclusions about trans-sector interoperability can be extracted and technological implications can be derived. Keywords: interoperability; MDA; sector; economic; model; productivity; service science; ATHENA; digital information network
1. Introduction IT systems interoperability is a growing interest area, mainly motivated by the need of integrating new, legacy and evolving systems [5]. Interoperability refers to the “ability of two or more systems or components to exchange information and to use the information that has been exchanged” [12]. The importance of interoperability has increased together with the adoption of Digital Information Networks (DINs). DINs refer to information networks supported by telecommunication infrastructures and terminated by microprocessors. DINs
124
A Madureira, F. den Hartog, E. Silva and N. Baken
support the digital economy: an economy that is based on digital goods and services in any of the production, distribution and consumption stages. According to the ATHENA framework [5], interoperability takes place, at least, at four levels: business, process, service and information. In this paper, we investigate trans-sector digital interoperability, which by definition involves interoperability across different economic sectors connected through DINs. We define sector as a cluster of organisations performing homogeneous activities. Sectors such as Healthcare, Education or Transport have different societal roles [1]. Therefore, enterprises from different sectors are inherently not competing in the same market, since they provide different products or services. Besides sectors operating in the same traditional value chains, the invisible hand of the markets does not lead enterprises to look across the boundaries of their own sector. With an upcoming interest in services science [20] and novel trans-sector business models [2], sometimes with more intangible social or environmental outcomes (e.g. eGovernment), a stronger driver arises to break the interoperability barriers across sectors. Bastiaansen and Baken [3] conceptualise two approaches for trans-sector interoperability: 1) top-down interoperability: the functionality to be realised must be leading in the IT system development process. Thus, the business requirements must be top-down translated into trans-sector implementations. A method for this approach is Model Driven Architecture (MDA) (e.g. the ATHENA framework); 2) bottom-up interoperability: trans-sector processes require the integration of the existing functions provided by the individual sectors. Such integration requires rich and unambiguous syntactic and semantic description of the IT functions provided by the sectors. A method for this approach is Semantic Web Services (SWS). The ATHENA framework gives a good starting point for designing a top-down interoperability model, but it should be taken from the enterprise plane to the economic sector plane. In this paper, based upon the ATHENA framework, we propose a novel model to address trans-sector digital interoperability. Particularly, we specify how the ATHENA framework should be adapted for the economic sector plane. With this model, we follow the top-down interoperability approach principle of identifying the business requirements before translating them into trans-sector implementations. Naturally, the model described is also useful in a bottom-up interoperability approach, because it helps to define syntactic and semantic descriptions of IT systems, potentially with direct business value. To validate the usefulness of the model, we describe how to derive technological implications from the application of the model. This paper is organised as follows. In section 1.2, we describe the state of the art regarding trans-sector digital interoperability. In section 1.3, we introduce a set of mechanisms that serves as the base for the model proposed in this paper. In section 1.4, we provide an overview of the complete model. Finally, in section 1.5, we draw some conclusions and indicate directions for future work.
Model for Trans-sector Digital Interoperability
125
2. State-of-the-Art Traditionally, scientific research on IT interoperability is a bottom-up process. Examples of this approach are semantic web service frameworks such as IRS-II [23], OWL-S [26] and WSMF [10]. Compared to IRS-II and OWL-S, WSMF takes a more business-oriented approach, focusing on a set of e-commerce requirements for Web services. But in practice, it lacks a top-down view of business requirements to make the components it describes (ontologies, goal repositories and mediators) more concrete for business purposes. Bottom-up semantic interoperability already evolved to standardisation efforts [13]. Motivation for this research comes from Virtual Enterprises (VE), Virtual Organisations (VO), Computer Supported Collaborative Work (CSCW), Workflow Management System (WFMS), Process-Centred Environments (PCEs), etc. ATHENA [5], a recent European project on interoperability, attempted a topdown approach. The uniqueness of this project lies in its multidisciplinary character, merging three research areas: 1) enterprise modelling to identify business requirements; 2) architectures and platforms to define implementation frameworks; and 3) ontologies to identify interoperability semantics. Figure 1 presents the ATHENA reference model indicating the required and provided artefacts of two connected enterprises. Interoperation can take place at various levels (enterprise/business, process, service and information/data). For each of these levels, a model-driven interoperability approach is prescribed where models are used to formalise and exchange the provided and required artefacts that must be negotiated and agreed upon.
Fig. 1 ATHENA reference model One ATHENA meta model is particularly relevant to our work: the Crossorganisational Business Process (CBP) model. The CBP tries to capture tasks and relationships from the different parties involved in cross-organisational business processes. One example of a process is a retailer-manufacturer cooperation: 1) a supplier sends a request for quotation to the manufacturer; 2) the manufacturer checks the stock; and 3) the manufacturer accepts the quotation and responds with an order. To our knowledge, no one has yet took the effort of breaking the meta concept of process into more refined terms, particularly at a general and complete, but necessarily abstract, economic plane. Here lies the value and originality of our work: breaking the concept of process at an economic trans-sector plane to be used
126
A Madureira, F. den Hartog, E. Silva and N. Baken
in an interoperability framework as the ATHENA. The novelty of our trans-sector approach for interoperability can be verified by a conclusion taken in [19]: the theoretical and empirical support for the relation between DINs and economic productivity is still inconclusive. Even economists focusing on understanding the economic importance of DINs, thus DINs' business value, still struggle to clarify it. In [19], a framework contributing to clarify this relation has been laid down which serves as the base for our trans-sector interoperability model described in this paper. Other projects have taken further action to meet the recognised need to clarify the concept of process for deriving technological requirements. Pratl et. al [27] introduce an eighth layer in the OSI model defining profiles for (manufacturing) control purposes. Bauer et. al [4] extend the OSI model with human factors, providing a conceptual tool to facilitate the discussions in human-computerinteraction disciplines.
3. Capabilities Productivity refers to a summarised measure of performance (P), based on the ratio of the total value of output (O) divided by the total value of input (I) (see [15]): P=O/I. In this section, we describe a set of mechanisms (defined as capabilities) which take an economic agent using DINs to a higher level of productivity. Any mechanism incrementing productivity leads to business value. Unlike mere operational functions (e.g. routing, forwarding, transferring, etc), the mechanisms identified are part of the interface between business and service. These mechanisms are generally applicable to economic agents across all sectors. Thus, they are the mechanisms required to identify a model for trans-sector digital interoperability. Before describing this set of mechanisms, we start by referring to the concept of externality to introduce a definition of economic agent. From here, follows a definition of capability, which is our conceptualisation of a direct causal mechanism linking DINs to sectoral productivity. Network externality can be defined as a change in productivity that an individual achieves when the number of other individuals using DINs changes. This allows, in principle, to separate the value of productivity into two distinct parts. One component, the autarky value, is the productivity value if there are no other individuals using DINs. The other component, the connection value, is the additional productivity value achieved when multiple other individuals are using DINs. The latter value is the essence of DINs' externality effects. Using the definition of connection value, we define economic agent in the following way: an economic agent is any entity from an economic environment which may achieve an additional productivity value when multiple other individuals are using DINs. Examples of agents are researchers using DINs to search for knowledge and companies marketing their products on-line. An agent explores personal and intrinsic capabilities to become more productive within his economic environment. For example, consumer A meets supplier B to acquire a production input at a lower price. The capability of A and B to meet each other will make both more productive. From a thorough literature review on the relation between information,
Model for Trans-sector Digital Interoperability 127
digital infrastructures and productivity, we have come across time and time again with a relevant set of six capabilities of a productive economic agent, which are directly dependent on DINs and impact productivity. We define capability as: capability is a quality of the economic agent used for productive purposes and directly effected by DINs. In the following subsections we describe these six capabilities, which are generally applicable to agents across all economic sectors. 3.1. Coordinativity Coordination is "the act of managing interdependencies between activities performed to achieve a goal" (see [21]). It arises, effecting productivity, when the agent has to choose between actions, the order of the actions matters and/or the time at which the actions are carried out matters. This leads to: coordinativity is the capability of an economic agent to manage interdependencies between activities with other agents to jointly achieve a common goal. Coordinativity prevents conflicts, waste of efforts, and squandering resources, and assures focus, while trying to accomplish a common goal. The work of Kandori et. al [16] has triggered much interest in coordination games. Important research results concern the impact of different network structures in coordination. In a survey, 45% of the respondents identified DINs as a driver to reorganise work practices (see [14]). More specifically, on-line remote monitoring can be seen as a good example of an application of digital coordination. 3.2. Cooperativity Cooperation can be defined as “acting together with a common purpose” (see [11]). Sharing information helps agents aligning their individual incentives with outcomes. Assuming proper behaviour, if absolute incentives are more advantageous over relative incentives, the agents cooperate. Both inter- and intraorganisational cooperation have been object of study since the work of Marshall [22]. Good examples are joint ventures. This leads to: cooperativity is the capability of an economic agent to align his personal goals with different individual goals from other agents for a common purpose. In practice, it is often hard to distinguish cooperativity from coordinativity. Conceptually, the main differences are: 1) in coordinativity the agents share exactly the same goals, while in cooperativity the agents share only partially aligned goals; and 2) in coordinativity the relation between the agents is critically dependent on time, while in cooperativity the agents relate to each other typically off-line. Although the experimental literature on cooperation is vast, only a few papers consider the role of networks in this process (see e.g. [31]). Supply and demand matching with on-line trading is an important practical example of the importance of DINs for cooperativity. 3.3. Adoptativity Nelson and Winter [24] state that firms improve their productivity by adopting technological and organisational solutions from the most innovative firms.
128
A Madureira, F. den Hartog, E. Silva and N. Baken
Examples are informal associations and product advertisement. Important dimensions to be accounted are the level of codification and the extent to which the knowledge fits in a set of interdependent elements. This leads to: adoptativity is the capability of an economic agent to adopt knowledge from other agents. There is a vast literature studying adoptativity using network analysis. It started with Ryan and Gross [28] studying adoption of pesticides by rural sociologists, and Coleman et. al [7] studying the adoption of medicines. Many examples could be cited showing the value of digital networks to exchange knowledge. A good example is e-learning between students. 3.4. Creativity Agents can increase their productivity by creating new knowledge following from collaborating with other agents to address operational inefficiencies. Their motivation to collaborate comes from their limited specialised knowledge and changes in their environment. Organisations that best address crucial information gaps through their information network structures may be more able to create novel knowledge. This leads to: creativity is the capability of an economic agent to create new knowledge, unknown to him before and to his collaborative agents. The relevance of DINs for collaborative research is well recognised (see [25]), and evidences have been found that organisations that use them more intensively, innovate more (see [17]). A trade-off exists between the rate of information gathering and the rate of environmental change. A good example of creativity is research in universities. 3.5. Selectivity Selection is the process of scanning for the unknown or generating courses of action that improve on known alternatives (see [6]). For maximal productivity, the agent has to decide for a stopping point in an uncertain environment, while keeping computational requirements within limits. This leads to: selectivity is the capability of an economic agent to scan and value information from other agents, generating courses of action that improve on known alternatives. The role of information networks has been extensively acknowledged in this process (see [32]). A practical proposal accounting the value of networks in the process of selection has been made by Saaty [29]. This framework has been used for interdependent information system project selection. On-line job hunting and Google.com are good examples of selectivity using DINs. 3.6. Negotiability Negotiability occurs when exchange happens between unfamiliar partners or when evaluating new courses of action. Negotiation grows in importance with the perception that potential downside effects of a wrong decision can be large and costly to reverse. Negotiability mechanisms include signalling (e.g. give guarantees to buy) and screening (e.g. give certificates to sell). Economic literature further distinguishes between one shot and repeated contracts. This leads to: negotiability
Model for Trans-sector Digital Interoperability 129
is the capability of an economic agent to bargain with other agents for lower exchange costs. Kranton and Minehart [18] developed a model in which the prices are determined by a bargaining process rather than an English auction. However, the precise influence of the network structure in negotiation processes has not been intensively studied yet. On-line stock trading activities are a good example of the importance of DINs for negotiability.
4. Trans-sector Interoperability Model Figure 2 resumes our model for trans-sector interoperability. Naturally, it is based upon the ATHENA model of figure 1, but specifies the general processes for the trans-sector (economic) plane. The processes are the capabilities referred in the previous section. In this context, it makes more sense to talk about inter-sector interactions rather than inter-enterprise interactions. Naturally, being sectors clusters of enterprises, these capabilities are also applicable to inter-enterprise interactions.
Fig. 2 Trans-sector interoperability model The scheme represents the four layers of sectors A and B: DINs and other IT (e.g. computer terminals), service, processes and business. The middle part shows the various capabilities/processes analysed in this paper, symbolising how exploiting these capabilities increases productivity when DINs are used for interaction between sectors. The capabilities are shown in random order. In the future, however, we would like to input some structure to the order of the capabilities. Intuitively, we would expect productivity to be more sensible to some of these capabilities. For example, creativity is a source for innovations which might have a profound effect on productivity. Selectivity, on the other hand, seems to be an input to other capabilities (e.g. adoptativity). Therefore, it might be more complicated to correlate data on selectivity with data on productivity. DINs are the infrastructure which enables the economic agents to use these capabilities to increase their productivity, regardless of the specific sectors they are dealing with on a case to case basis. These capabilities are generally applicable to agents across all economic sectors. Therefore, at an aggregated macro level, our model may help to manage and control trans-sector interoperability, productivity, and innovation on a national or even global scale from a capabilities point of view.
130
A Madureira, F. den Hartog, E. Silva and N. Baken
Figure 3 is an attempt to quantify the importance of coordinativity and adoptativity for different economical sectors. The data source used is the Eurostat survey on ICT usage and e-Commerce in enterprises [9]. The amount of data is quite significant, spanning the years from 2002 to 2008, various countries from EU, with regional and sectoral breakdowns, for a large collection of different aspects related to the use of ICT in enterprises. For this paper, only data from 2007 for the Netherlands has been used. For both subfigures, the proxy variable used for DINs is “have access to Internet” (reference is e_iacc). For coordinativity, the proxy variable used is “use of systems for managing production, logistics or service operations (reference is e_lnkpls). For adoptativity, the proxy variable is “purpose of the Internet (as a customer): training and education” (reference is e_iedu). The numerical references in the figures (e.g. 10+:72) refer to more refined aggregations of enterprises (e.g. a particular type of manufacturing enterprises).
Fig. 3 Importance of coordinativity (top) and adoptativity (bottom) per sector The limitations of the data only allow us to take preliminary and exemplifying conclusions. For example, coordinativity seems to be more important for the manufacturing sector than for real estate, renting and business activities sector. The inverse could be said for adoptativity: the manufacturing sector performs less online training and education than the real estate, renting and business activities
Model for Trans-sector Digital Interoperability
131
sector. These figures could be considerably improved at least in three ways: 1) the Eurostat only collects data for particular economic sectors (e.g. manufacturing). Other sectors are not observed (e.g. the education sector). For a full overview of trans-sector interoperability, all the sectors should be evaluated; 2) the sector classification used is the Classification of Economic Activities in the European Community (NACE). Some sectors classified are hardly understandable (e.g. the “production” sector). There is no worldwide consensus is any classification, and furthermore, classifications evolve over time as the relevance of specific activity clusters varies. A proper sector classification has to be used that discriminates sectors in a clear and relevant way. Worldwide, the UN International Standard Industrial Classification (ISIC) [30] classification seems to be the preferred one; and 3) the proxies used for the capabilities should be composed measures of various available data source variables. E.g. coordinativity could also have been measured with the variable “use invoicing and paying systems” (reference is e_lnkpay). After understanding which capabilities are more relevant for the different sectors, a survey to IT departments of representative enterprises of the different sectors could be done to investigate which IT applications are commonly used to address those capabilities (e.g. online agenda applications for coordinativity). Finally, these IT applications should be analysed concerning the fulfilment of interoperability requirements (e.g. use of open standards). Hence, conclusions could be extracted concerning the status of trans-sector interoperability. Furthermore, technological requirements for those IT applications could be derived to increase trans-sector interoperability. The procedure described in the previous paragraph will be used in our future work.
5. Conclusion and Future Work Generally, we conclude that current interoperability architectural models do not take a full top-down approach when translating business requirements into technological implementations. The ATHENA model gives a good starting point for designing such a top-down interoperability model, but it should be taken from the enterprise plane to the economic sector plane. One of the model's levels requiring adaptation is the processes level. To address the economic plane of interoperability, we propose a trans-sector interoperability model based upon a set of mechanisms (defined as capabilities) which take an economic agent using DINs to a higher level of productivity. Any mechanism incrementing productivity leads to business value. Unlike mere operational functions (e.g. routing, forwarding, transferring, etc), the mechanisms identified are part of the interface between business and service. These mechanisms are generally applicable to economic agents across all sectors. Thus, they are the mechanisms required to identify a model for trans-sector digital interoperability. Using data from the Eurostat survey on ICT usage and eCommerce in enterprises, we have made a preliminary attempt to quantify the importance of two capabilities (coordinativity and adoptativity) for different economical sectors. Although their relative relevance and orthogonality should still
132
A Madureira, F. den Hartog, E. Silva and N. Baken
be investigated, from our thorough literature review, we are confident to state that these capabilities most probably form a complete set. However, it should be noted that we only took economic capabilities into account. Human and social factors are also important, but are not yet included. Our future work goes along six directions: 1) the capabilities described in this paper are used by an economic agent to rationally navigate through a production space problem. However, other factors are affected by DINs that, indirectly, affect productivity, particularly human (e.g. limitations in information sensing) and social factors (e.g. trust). Thus, further development of the model is required to include these factors; 2) we aim to functionally decompose the capabilities of the model to test if they overlap. From here, commonalities between the capabilities might be revealed; 3) further integration of the model with the top-down interoperability framework ATHENA; 4) perform a thorough analysis to understand which capabilities are more relevant for the different sectors; 5) perform a survey to representative enterprises from different sectors to understand which IT applications are commonly used to address the capabilities, and analyse these IT applications concerning the fulfilment of interoperability requirements; and 6) extract conclusions about transsector interoperability and derive technological requirements for IT applications to increase trans-sector interoperability.
6. References [1]
N.H.G. Baken, N. van Belleghem, E. van Boven, and A. de Korte. Unravelling 21st Century Riddles -Universal Network Visions from a Human Perspective. The Journal of The Communication Network, 5(4):11– 20, 2007. [2] N.H.G. Baken, E. van Boven, and A.J.P.S. Madureira. Renaissance of the Incumbents: Network Visions from a Human Perspective. eChallenges 2007 Conference, The Hague, The Netherlands, October 2007. [3] H.J.M. Bastiaansen and N.H.G. Baken. Using Advanced Integration Concepts for Trans-sector Innovation- View and Status. In Proceedings of the FITCE Conference, 2007. [4] J.M. Bauer, P. Gai, J. Kim, T.A. Muth, and S.S. Wildman. Broadband: Benefits and Policy Challenges. Technical report, Quello Center for Merit Network Inc., 2002. [5] A. Berre, B. Elvesæter, N. Figay, C. Guglielmina, S. Johnsen, D. Karlsen, T. Knothe, and S. Lippe. The ATHENA Interoperability Framework. In Enterprise Interoperability II: New Challenges and Approaches, pages 569–580. Springer, 2007. [6] N. Bulkley and M. Van Alstyne. Why Information Should Influence Productivity. Working Paper Series 202, MIT Sloan School of Management, 2004. [7] J.S. Coleman, E. Katz, and H. Menzel. Medical Innovation: A Diffusion Study. New York: Bobbs-Merrill, 1966. [8] F. den Hartog, M. Blom, C. Lageweg, M. Peeters, J. Schmidt, R. van der Veer, A. de Vries, M. van der Werff, Q. Tao, R. Veldhuis, N. Baken, and F. Selgert. First experiences with Personal Networks as an enabling platform for service providers. In Proceedings of the Second Workshop on Personalized Networks, 2007. [9] Eurostat. ICT usage and e-Commerce in enterprises. http://epp.eurostat.ec.europa.eu/portal/page/portal/information, 2009. [10] D. Fensel and C. Bussler. The Web Service Modeling Framework WSMF. Electronic Commerce Research and Applications, 1(2):113–137, 2002.
Model for Trans-sector Digital Interoperability
133
[11] Z. Hua. Study of Multi-Agent Cooperation. In Proceedings of Third International Conference on Machine Learning and Cybernetics. IEEE, 2004. [12] IEEE. IEEE standard computer dictionary : a compilation of IEEE standard computer glossaries. IEEE Computer Society Press, 1991. [13] ISO. Industrial automation systems and integration- Manufacturing software capability profiling for interoperability. Standard 16100, ISO, 2002. [14] P. James and P. Hopkinson. Sustainable broadband? The Economic, Environmental and Social Impacts of Cornwall’s actnow Project. Technical report, University of Bradford and SustainIT, 2005. [15] D.W. Jorgenson and Z. Griliches. The Explanation of Productivity Change. Review of Economic Studies, 34:349–383, 1967. [16] M. Kandori, G.J. Mailath, and R. Rob. Learning, Mutation, and Long Run Equilibria in Games. Econometrica, 61(1):29–56, 1993. [17] P. Koellinger. Impact of ICT on corporate performance, productivity and employment dynamics. Technical Report Industry, Special Report No. 01/2006, e-Business Watch, European Commission and DG Enterprise, 2006. [18] R. Kranton and D.F. Minehart. A Theory of Buyer-Seller Networks. American Economic Review, 91(3):485–508, 2001. [19] A. Madureira, N. Baken, and H. Bouwman. Towards a Framework to Analyze Causal Relations From Digital Information Networks To Micro Economic Productivity. World Congress on the Knowledge Society, Venice, Italy, 2009. [20] P. Maglio and J. Spohrer. Fundamentals of service science. Journal of the Academy of Marketing Science, 36(1):18–20, 2008. [21] T.W. Malone and K. Crowston. What is coordination theory and how can it help design cooperative work systems? In CSCW ’90: Proceedings of the 1990 ACM conference on Computer-supported cooperative work, pages 357–370. ACM Press, 1990. [22] A. Marshall. Principles of Economics. London: Mcmillan, 1890. [23] E. Motta, J. Domingue, L. Cabral, and M. Gaspari. IRS-II: A Framework and Infrastructure for Semantic Web Services. In The SemanticWeb - ISWC 2003, pages 306–318. Springer Berlin/Heidelberg, 2003. [24] R.R. Nelson and S.G. Winter. Evolutionary Theory of Economic Change. Belknap Press, 1985. [25] OECD. OECD Broadband Portal. http://www.oecd.org/sti/ict/broadband, 2008. [26] OWL-S Coalition. OWL-S 1.0 Release. Website, 2003. http://www.daml.org/services/owl-s/1.0. [27] G. Pratl, D. Dietrich, G. Hancke, and W. Penzhorn. A New Model for Autonomous, Networked Control Systems. Industrial Informatics, IEEE Transactions on, 3(1):21– 32, 2007. [28] B. Ryan and N.C. Gross. The Diffusion of Hybrid Seed Corn in Two Iowa Communities. Rural Sociology, 23:15–24, 1943. [29] T.L. Saaty. The Analytic Network Process: Decision Making with Dependence and Feedback. RWS Publications, 2001. [30] UN. International Standard Industrial Classification of all Economic Activities (ISIC) Revision 3.1. Statistical Paper ST/ESA/STAT/SER.M/4/Rev.3.1, United Nations, 2002. [31] F. Vega-Redondo. Building Up Social Capital in a Changing World. Discussion paper, University of Alicante, 2002. [32] D. J. Watts, P. S. Dodds, and M. E. J. Newman. Identity and Search in Social Networks. Science, 296:1302, 2002.
Transformation from a Collaborative Process to Multiple Interoperability Processes Hui Liu1, 2 and Jean-Pierre Bourey1, 2 1 2
Université Lille Nord de France, F-59000 Lille, France Ecole Centrale de Lille, Laboratoire de Modélisation et de Management des Organisations, Cité Scientifique – BP 48 – 59651 Villeneuve d’Ascq Cedex, France
Abstract. This paper defines some important concepts in the domain of enterprise interoperability, and based on these concepts, it proposes a method to solve the enterprise interoperability problem. This paper elaborates in detail one of the steps included in the method: the transformation from collaborative process to interoperability processes. The transformation is based on the definition of the concept “rank of interoperability process” that makes it possible to analyse the relationships between three kinds of interoperability processes. Keywords: collaborative process, interoperability process, transformation, rank of interoperability process
1. Introduction To meet the business objectives, enterprises need to collaborate with other enterprises, which will raises their own added value and improves their competitiveness greatly. How to support such collaboration by information systems of all the related enterprises is a big problem, and it is described as the enterprise interoperability problem. However, the information systems (IS) of the related enterprises are usually distributed heterogeneous, so the foundation of this problem is how to make such information systems exchange information and understand and use the exchanged information. For the aspect of information exchange, some protocols and standards for describing communication method and information format have been proposed and widely used, for example, TCP/IP, HTTP, JMS, XML and SOAP and so on; and to support the information exchange at the enterprise-level, some middleware and architecture styles have also been proposed, such as EAI, CORBA, ESB, P2P, SOA (web service, RESTful service [7]) and SMDA (Service Model Driven
136
H. Liu and J.P. Bourey
Architecture)[12]. For the aspect of information understanding, lots of ontology languages have been proposed, for example, OKBC, OIL, OWL-S1, WSMO, WSDL-S, SAWSDL, PIF[10], some of which are XML-based, some are not and some of which are used to represent knowledge, some are used to describe internet resources and some are used to describe business processes. For further study of enterprise interoperability, [5] describes a roadmap, which includes three key areas: 1) enterprise modelling, 2) architecture and platform and 3) enterprise ontology. This roadmap is supported by the efforts of several European projects, including ATHENA, INTEROP, Ecoleader2, etc. We can see that the above foundation of enterprise interoperability is included in the second and third points of the roadmap and they have been researched deeply. Instead, this paper will research collaboration between enterprises from the viewpoint of enterprise modelling. The collaboration between enterprises is described in a collaborative business process, which is a process describing the collaboration requirements and whose activities are supported during implementation, by at least two information systems. Each of these systems performs the implementation of the collaborative business process, called interoperability process and when executing the interoperability process, each of the systems will communicate with other systems. So an interoperability process is defined as a process containing at least one activity of information exchange, called interoperability activity. In section 2, this paper proposes a method which describes how to transformation a collaborative business process into an executable interoperability process. In section 3, this paper elaborates in detail an important transformation step in the proposed method. Finally the conclusion summarizes the contributions and describes the future work.
2. Terminology Definition In Section 1, collaborative business process is used to model the collaboration requirements between enterprises and it is implemented by interoperability process after some steps of transformation. According to the MDA framework defined in [4], we can see that collaborative process belongs to the level CIM and interoperability process belongs to PIM and PSM. The actors in collaborative business process can be enterprises or departments, and such actors are defined as collaborators; and the actors in interoperability process can be information systems, sub-systems, components or services, they are defined as participants. So we can get Table 1.
1. [OWL-S] http://www.daml.org/services/owl-s/; [WSMO] http://www.wsmo.org/; [WSDL-S] http://www.w3.org/Submission/WSDL-S/; [SAWSDL] http://lsdis.cs.uga.edu/projects/meteor-s/SAWSDL/ 2. http://www.athena-ip.org; http://www.interop-vlab.eu/; http://ecolead.vtt.fi/
Transformation from a Collaborative Process to Interoperability Processes 137 Table 1. Relationship of the concepts about interoperability problem with MDA MDA level
Actor
Business process
CIM
Collaborator
Collaborative process
PIM, PSM
Participant
Interoperability process
To further analyze the enterprise interoperability problem, we analyze the classification of business processes. [6] has proposed several criteria to classify the business processes. This paper will classify the business process according to the following criterion: the quantitative relationship between the owners and controllers of the business activities in a business process. The owner of business activity is the actor who is responsible for performing this activity; the controller is the actor who starts the activity. Following the above criterion, there are three kinds of processes in or between the enterprises’ IS: 1. The internal process: it is composed of the activities which belong to the same IS of an enterprise; 2. The coordination process: it is composed of the activities some of which take place between several IS and/or enterprises, but the process execution is owned and controlled by only one IS and/or enterprise; 3. The cooperation process: it is composed of the activities some of which happen between several IS and/or enterprises and the process execution is owned and controlled by several IS and/or enterprises, but each IS and/or enterprise can only control the execution of its own activities. For the collaborative process, if it is the internal process, i.e., the process is across different departments in one enterprise, the collaborator is just the enterprise itself; if it is the coordination process, the collaborator who controls the process execution is named the coordinator (or mediator), other collaborators are named passive collaborator; if it is the cooperation process, the collaborator who controls the process is named principal cooperator and the collaborator who controls its own activities but doesn’t control the process is named secondary cooperator. For each of the above three processes, if one of its activities is the interoperability activity, then the process is an interoperability process. At first, the two latter types of processes may be interoperability processes. In addition, in the case of an internal process, it may be necessary to implement the information exchanges between some modules of enterprises’ IS. These exchanges are carried out by the activities that can be considered as internal interoperability activities. Hence, the three types of processes may be interoperability processes. For the interoperability process, if it is the coordination process, its participants can play the roles “requester” and “provider”; if it is the cooperation process, its participants can play the roles “requester” and “provider”, “subscriber” and “publisher”; if it is the internal process, it can be executed as coordination process or cooperation process and its participants can be that of coordination or cooperation process.
138
H. Liu and J.P. Bourey
3. Proposed Method to Solve Enterprise Interoperability Problem According to terminologies defined in the precedent section, the following method is proposed to solve interoperability problem, illustrated in Figure 1. Collaborative Process Collaborative Process Annotated with information of collaborators PoIM1- Interoperability Process (Fix part of messages’ types; map collaborators to participants; divided into N sub-processes)
Ontology
PoIM2- Interoperability Process (Message; search the participants for activities)
PoSM- Interoperability Process (Implemented in process specification language)
Execution engine of business process (process language; algorithm) Infrastructure (Cloud Computing) Figure 1. Proposed method to solve enterprise interoperability problem
At the first level “Collaborative Process”, the collaborative process must be constructed from two aspects: business flow and data (message) flow, which is inspired by [8]. In [8], US Army, proposed an expansion of the system architecture into three further sub-architectures: software architecture, data architecture and network architecture. The software architecture defines the functionality of each modular, and the data architecture is related with data definition, and the network architecture is related with software deployment requirement. Furthermore, all business requirements must be mapped into a certain system architecture if it want to be implemented and the collaborative process is one kind of business requirements, so collaborative process must also be mapped onto the above three sub-architectures, that is to say collaborative process must have some aspects that can be mapped onto the above three sub-architecture. However, the network subarchitecture is determined by the concrete business requirements, in this paper we don’t discuss about it, but it’s still very important; so finally we will construct the collaborative process from two aspects: the business flow describing the functionality of the collaborative process, and the data flow describing the exchanged data in the process. At the second level, the collaborative process will be annotated with the information of collaborators, i.e., all the activities in the process must be charged by one collaborator. This task depends on the ontology base. When searching the corresponding collaborator for a certain activity, the ontology base will be inspected to determine which collaborator can do such activity. If several candidates are selected, the target candidate will be fixed according to the
Transformation from a Collaborative Process to Interoperability Processes 139
collaboration policy/requirements, or according to the predefined conditions, such as QoS, trust rank/belief value etc. So ontology base must contain such information of all the collaborators (for example, collaborator’s name, historical information about its service offering, what it is responsible for, etc). At the third level “PoIM1” (Protocol Independent Model 1), the types of some messages in the collaborative process can be determined according to messages’ context (messages’ sender and receiver, and relevant business activities). The information about some messages’ types may also be explicitly declared in the data flow of collaboration process. These two cases for message type determination are based on ontology base. So ontology base must contain the definitions of business messages which have some context specifications of their usages. After that, the collaborators in the collaborative process will be mapped onto participants. The key of the mapping from collaborator to participant of an activity depends on the activity’s functionality and context. After the mapping, the collaborator’s information in the process must still be kept, because such information has some semantics that are not implied in participants, for example, there are several roles of collaborators, whose semantics can’t be represented by participants’ roles. The above task also relies on the ontology base. So the ontology base must also contain the information about each collaborator’s system architecture because the participant is an element of system architecture. After some messages’ types is fixed and the mapping from collaborator to participant is done, the collaborative process becomes the interoperability process, and then the interoperability process will be transformed to a set of interoperability sub-processes according to a certain transformation method which will be elaborated in detail in section 1.4. At the fourth level “PoIM2” (Protocol Independent Model 2), the messages whose types haven’t been determined will select their types and each participant will be mapped to a concrete service. This step is also based on ontology base and the ontology base must contain the definitions about messages and services. At the fifth level “PoSM” (Protocol Specific Model), the interoperability process will be implemented in a certain executable process specification language. We can see that the above proposed method depends closely on ontology base and SOA, and it also has one precondition: the interoperability process’s realization totally depends on the original functions of each collaborator’s information system. Of course the above method also relies on the process execution engine and a certain infrastructure, such as cloud computing infrastructure.
4. Interoperability Process The composition of interoperability activities constitutes the interoperability process, which is determined by the collaboration requirements between enterprises and generated from collaborative process. The interoperability process is used to express the application-application business process [6] and can be implemented directly in a programming language (Java, C + +, etc.), or a processes specification language (WS-CDL[9], WS-BPEL[2], workflow model etc). As the
140
H. Liu and J.P. Bourey
development mode of information systems has been shifted from “programming” to “assembly” and from “data-centric” to “process-oriented” [6], the interoperability process tends to be expressed in process specification language. In addition, the use of workflow tools is limited to specific industries, such as banking and insurance [11]. Furthermore, Web services are interesting to software vendors and scientists for architecting and implementing business collaborations within and across organizational boundaries [1]. So it will be a trend to adopt the web servicerelated process specification languages to express the interoperability process, for example, BPMN, which can be transformed into WS-BPEL process using the mapping method proposed in the BPMN specification V1.2. In the following subsections, a method to generate the interoperability process is proposed. This method is based on annotated BPMN diagrams. As the execution of internal business process or coordination business process is controlled by only one enterprise, and it is only related with a series of information exchanges with their partners, so it is easy to implement with the help of WS-BPEL or workflow model. The following two subsections will focus on the cooperation process. In addition, in order to simplify our discussion, collaborative process and interoperability process in the following subsections only contain their business flow (data flow is omitted), and in interoperability process, the participants of all activities are the corresponding collaborators (because of the lack of sufficient information, such mapping can’t be done), and we assume that some messages’ types in collaborative process can be determined according to a certain ontology architecture, i.e., the cooperation process as collaborative process can be transformed into interoperability process. 4.1. Rank of Interoperability Process In the cooperation process, it is assumed that 1 there are N cooperators in the process, N>=2; 2 if the process is launched, all the cooperators will follow the process to carry out corresponding activities, so all cooperators must know clearly the state of the process execution; 3 the continuous activities of the same cooperator in the process can be merged into one activity node who delegates a sub-process of the corresponding cooperator, then the cooperation process can be changed into a new process with “sub-process” nodes and it has the following property: in the process each two neighboring activity nodes belong to the different cooperators. A transformation example is given in Figure 2.b which is obtained from Figure 2.a by merging B.T11 and B.T12 into B.T1 and merging C.T31 and C.T32 into C.T3. In Figure 2, the name of each activity has the format X.YZ, where X indicates the owner of the activity, Y indicates the activity type and Z is the identifier of the activity. Particularly before the transformation from Figure 2.a to Figure 2.b, some messages’ types in Figure 2.a have been fixed.
Transformation from a Collaborative Process to Interoperability Processes
141
a A collaborative process with the continuous activities that belong to the same cooperator
b An interoperability process without the continuous activities that belong to the same cooperator Figure 2. Cooperation Process in BPMN
To characterize the complexity of interoperability, we distinguish two essential characteristics: the number of owners for interoperability activities (called the rank of interoperability process, noted as R) and the number of controllers for interoperability processes (noted as NCP). As all normal activities in the interoperability process must belong to a collaborator, but the collaborators may not necessarily control the interoperability process, the number of controllers for interoperability process will be less than or equal to R. If the number of process controllers is 1, i.e., if only one enterprise is responsible for controlling the collaborative process, the process is actually an internal process or a coordination process. If the rank is greater than 1 and the NCP is 1, the process is a coordination process. Table 2 shows the precedent relationship. Table 2. Relationship between three kinds of processes and their rank Business Process
Rank
NCP
Internal Processus
R=1
NCP=1
Coordination Processus
R>1
NCP=1
Cooperation Processus
R>1
NCP<=R but NCP>1
Then the following question will be more interesting: how to decline the rank of the interoperability process? In Figure 2.b, its R is equal to 4 and the designer has defined A and B as principal cooperators, and C and E as secondary cooperators. The two branches of the gateway G1 are related with cooperators B and C. They can be replaced with two sub-processes (cf. Figure 3), and the 4 interoperability
142
H. Liu and J.P. Bourey
sub-processes of Figure 2.b (i.e. B.T1ÆC.T2ÆB.T3/C.T4, C.T1ÆB.T2ÆC.T3, A.T1ÆE.T1 and E.T2ÆA.T2) are replaced with B.P1, B.P2, A.P1 and A.P2, so the rank of the obtained process is 2 (cf. Figure 3). Finally, the cooperators A and E have two sub-processes corresponding to (A.T1ÆE.T1) and (E.T2ÆA.T2). Meanwhile, the cooperators B and C have two sub-processes (B.T1ÆC.T2ÆB.T3/C.T4) and (C.T1ÆB.T2ÆC.T3). The cooperators B and C have one internal process separately: (B.T11ÆB.T12) and (C.T31ÆC.T32). The cooperators A and B also have one cooperation process illustrated in Figure 3.
Figure 3. Simplifed cooperation process in BPMN
The interoperability process transformation from Figure 2.a to Figure 2.b and then to Figure 3 must respect the following principles: 1. 2. 3.
The rank of target interoperability process must be less than that of the source interoperability process; The rank of any generated interoperability sub-process must be less than or equal to that of the target interoperability process; The rank of the target interoperability process must be more or equal to 2.
According to the transformation described previously, we can see that the global cooperation process (Figure 3) becomes simpler, and at the same time new sub-processes are generated: the transformation simplifies the implementation of cooperation process, but meanwhile, it will increase the management complexity of the interoperability process. Are there other benefits brought from the transformation? To answer this question, we will analyze the execution of the cooperation process between enterprises in the following section. 4.2. Execution of interoperability process To illustrate the execution of the cooperation process, consider the cooperation subprocess B.P1 in Figure 3, whose detail is given in Figure 4.
Figure 4. Cooperation sub-process - B.P1
Transformation from a Collaborative Process to Interoperability Processes
143
As B.P1 is owned and controlled by cooperators B and C, this paper offers the following execution process of the process B.P1: 1. 2. 3. 4.
5.
6.
When B.P1 is invoked, a participant, for example B, will create the instance of B.P1, and meanwhile it informs all the other cooperators (cooperator C) to create the instance of P1 in their own IS; After all the cooperators have completed the instantiation of P1, then execute the following steps; Each cooperator will check which cooperator executes the next activity, if B finds that it charge the execution of B.T1, then it will execute it and all the other cooperators (C) will wait for the notification from B; If all the other cooperators (C) receive the notification from B, then each cooperator will check which cooperator executes the next activity, if C finds that it charges the execution of C.T2, then it will execute it and all other cooperators (B) will wait for a notification from C; If all the other cooperators (B) have received the notification from C, then each cooperator will check which cooperator will execute the next activities (B.T3 and C.T4), if B finds that it will execute B.T3 and C finds that it will execute C.T4, then all the other cooperators (C and B) will wait for notifications from B and C; If all the other cooperators (C and B) have received notifications from B and C, then the execution process ends.
As described earlier, the executions of the cooperation process at different cooperators are synchronized and collaborative. All the relevant cooperators follow the same method to execute the cooperation process, but in the IS of each cooperator, the execution behaviour is different. If any cooperator retreats from cooperation process or if any notification is not received by a target cooperator, the execution of the process will be blocked or abort. If any kind of failures comes out during the process execution, some measures must be taken to make the process execution recover from the failure or make the process execution stop elegantly. So, the execution engine of cooperation process should be based on distributed computing and message-oriented computing [3]. In addition, as all cooperators have been determined before the design and implementation of cooperation process, the cooperation process can satisfy the requirements of “static” collaboration between enterprises, i.e., all the collaborators have the fixed relationship. If the collaboration is dynamic, i.e., some collaborators can often be replaced by other candidates, the cooperation process in this paper is not able to meet such requirement directly. However, the cooperation process can be extended to support dynamic collaboration. Firstly, at the level of business modelling, the cooperation activity belongs to a role, not to a cooperator, and a role can have several cooperator candidates; secondly, during the execution of the cooperation process, if a member quits, the execution promoter will choose another candidate whose role is the same as that of the quitting cooperator. After the introduction of the interoperability process’ execution, we can see, the transformation which reduces the rank of the cooperation process can reduce many notifications between cooperators.
144
H. Liu and J.P. Bourey
5. Conclusion This article has proposed a method to align collaboration requirements with technology capability. Particularly, this article has illustrated in detail the transformation from collaborative process to interoperability process. This transformation is based on the definition of the concept “rank of interoperability process” and allows making information exchanges between hierarchical processes. The future research focuses firstly on semantic annotations of exchanged information and participants, and secondly on the formalization of the transformation algorithm (from the collaborative process to a set of interoperability process) which will rely on the formalization of enterprise architecture and the formal expression of collaboration process and interoperability process.
6. References [1]
Alonso G., Casati F., Kuno H., and Machiraju V., Web Services Concepts, Architectures and Applications, Springer-Verlag, Berlin, 2004. [2] Alve A., Arkin A., et al. OASIS Web Services Business Process Execution Language Version 2.0. April 11 2007. http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0OS.html [3] Berre A.-J., State of the art for interoperability architecture approaches, Nov 19, 2004, http://www.interop-noe.org [4] Bourey J.-P., Grangel Seguer R., Doumeingts G., Berre A.-J., Deliverable DTG2.3 Report on Model-Driven Interoperability, 15 Mai, 2007, http://interopvlab.eu/ei_public_deliverables/interop-noe-deliverables/dap-domain-architecture-andplatforms/D91/ (Accessed on March 17 2009) [5] Chen, D., Doumeingts, G., “European Initiatives to develop interoperability of enterprise applications - basic concepts, framework and roadmap”, Journal of Annual reviews in Control, 27 (3), 151-160, Elsevier, December 2003. [6] Dumas M., van der Aalst W.M.P., and ter Hofstede A.H.M., Process-Aware Information Systems: Bridging People and Software through Process Technology, Wiley& Sons, 2005. [7] Fielding Roy T.. “Architectural Styles and the Design of Network-based Software Architectures”. Ph.D. dissertation, 2000.http://portal.acm.org/citation.cfm?id=932295 [8] Hamilton John A.. “A practical application of enterprise architecture for interoperability”. ISE '03. ISBN: 1-56555-270-9. http://www.scs.org/getDoc.cfm?id=2227 [9] Kavantzas N., Burdett D., et al. W3C Web Services Choreography Description Language Version 1.0. Nov 9 2005.http://www.w3.org/TR/ws-cdl-10/ [10] Polyak S., Lee J., Gruninger M., and Menzel C., “Applying the process interchange format (PIF) to a supply chain process interoperability scenario”, ECAI’98, Brighton, England, 1998. [11] van der Aalst W M. P., Benatallah B., Casati F., Curbera F., Verbeek E., “Business process management: Where business processes and web services meet”, Data Knowl. Eng. 61(1): 1-5 ,2007. [12] X. F. Xu, T. Mo and Z. J. Wang. “SMDA: A Service Model Driven Architecture”. Enterprise Interoperability II-New Challenges and Approaches. Springer-Verlag London Limited. 2007.ISBN: 9781846288579.p291-302
Part III
Semantics for Enterprise Inoperability
A Manufacturing Foundation Ontology for Product Life Cycle Interoperability Zahid Usman1, Robert I.M. Young1, Keith Case1, Jenny A. Harding1 1
Loughborough University-Wolfson School of Mechanical & Manufacturing Engineering, Loughborough, Leicestershire, UK
Abstract. This paper presents the idea of a proposed Manufacturing Foundation Ontology (MFO) aimed at acting as a basis for the Product Life Cycle (PLC) interoperability. MFO is aimed to have the provision for introducing interoperability not only across departments but across organization as well. The proposed idea shows the development of a MFO in several layers and various levels in those layers. The foundation ontology will act as a basis for building Interoperable knowledge bases or ‘World Models’ from a library of formally defined concepts in a heavy weight ontology. MFO must be flexible enough to allow organizations to be able to model their own domains with the flexibility to use the terms they want. Rules and axioms governing each and every concept add rigour to the semantics of the MFO and restrict the use of concepts to facilitate interoperability with a minimum effect on flexibility to model. Keywords: Business Interoperability requirements, meta-modelling for Interoperability, foundation Ontology, semantic mediation and enrichment, Product Life Cycle Interoperability
1. Introduction Manufacturing is and will be one of the top revenue and employment generators in Europe. According to a European commission report manufacturing in European Union (EU) is responsible for nearly 22% of the GNP, about 75% of total GDP and 70% of the employment [1]. In 2005, 2.3 million enterprises in the EU-27 had manufacturing (NACE Section C, D, I and K as quoted by [2]) as the main activity, having generated EUR 6,323 billion turnover, value added production of 1,630 billion and having employed 34.6 million of human resource [1,3] The role of computers in industry has increased exponentially and the Information and Communication Technologies (ICT) have become an integral part of almost every organization. Organizations all around the world have entered into a new era of ICT. Manufacturing organizations have moved from traditional
148
Z. Usman, R.I.M. Young,K.Case, J.A. Harding
manual drawings and design to the Computer Aided Technologies (CAx). Most expensive of tests have been replaced by computer simulations. Not only from the products perspective but also from the organizational point of view tools and techniques like Enterprise Resource Planning (ERP) e.g. Oracle, SAP, etc. Manufacturing and Materials Resource Planning (MRP) and several others to Manage PLC activities assisting from minor to major activities are being rapidly progressing. According to a report in 2005 [4] on ICT for Manufacturing, ICT are key to the manufacturing competence, competitiveness and jobs in Europe. Interoperability is defined by Ray & Jones [5] “the ability to share technical and business data, information and knowledge seamlessly across two or more software tools or application systems in an error free manner with minimal manual interventions”. With number of software tools being developed in parallel in different companies around the globe, it also raises the problem of interoperability across them. Organizations would need to interoperate internally as well as externally to take competitive advantage. To highlight the importance of interoperability a study by Brunnermeier and Martin [6] in 1999 at NIST showed that one billion U.S. $ per year are spent by U.S. automotive sector alone for solving interoperability problems. The multiples of this amount when including other sectors like, services, health care, electronics, logistics, telecommunication, aerospace, etc and not across U.S. only the figures would definitely highlight this as a major problem. This highlights the need to have an interoperability system which minimizes the cost incurred on solving interoperability problems. In the development of interoperability systems it is of extreme importance to formally capture & incorporate the semantics of the concepts. As highlighted through a survey by Tan and Madnick [7] that almost 70% of the total costs of interoperability projects is spent on identifying and locating semantic mismatches and developing the code to map them. Semantics are important for the foundation of a well organised hierarchy of concepts, the relations between them and rules governing their use. This study highlighted the need to incorporate the semantics or formalized meanings of concepts in ICT including PLC Management (PLM). The need for formal semantics leads to the need for heavy weight ontologies. Semantic formalization converts a simple hierarchy and dictionary of concepts or light weight ontology to a heavy weight ontology. Several definitions of ontology which is a borrowed term from philosophy can be found in the literature. The most quoted definition is by Gruber in 1993 [8] and several others e.g by Uschold & Gruninger in 1996 [9], Guarino [10] and Borst in 1997 [11], Studer et al 1998 [12], Schlenoff [13], et al and Roche in 2000 [14], Noy & McGuinness in 2002 [15] and Blomqvist & Ohgren in 2007 [16]. The one we prefer is given in the Process Specification Language(PSL) standard (ISO-18629) [17] as “a Lexicon of the specialized terminology along with some specifications of the meanings of the terms involved.”
2. The Requirement for a Manufacturing Foundation In this section business interoperability requirements are explored first from a systems’s perspective and then from the perspective of design and manufacturing.
A Manufacturing Foundation Ontology for Product Life Cycle Interoperability 149
2.1. A System’s Perspective on Interoperability The present typical approach for developing multiple integrated systems can be represented in the context of Model Driven Architectures (MDA) as shown in fig.1 a. This starts from a computational independent model (CIM) which defines the requirements for a system. From the CIM a Platform Independent Model (PIM) is developed and then the PIM is transformed into several platform specific models (PSMs). An example of this can be seen in the use of STEP [18]standards as PIM models supporting multiple CAD specific PSMs. However in our approach we want to provide the flexibility of multiple PIMs but still support interoperability. We argue that this can be achieved as long as all PIMs which are to interoperate share a common set of foundation concepts in their development as illustrated in figure 1 b. Because this approach offers flexibility in the definition of the PIM there is a need for a verification mechanism across the PIMs to confirm the level of interoperability which is possible.
a
b
Fig. 1. a. MDA approach to Interoperability; b. Requirement of Foundation Concepts for MDA
2.2. Design and Manufacturing Perspectives on Interoperability This research work is focussed on interoperability between design and manufacture and is undertaken in conjunction with manufacturing companies from the aerospace and automotive sectors. From our work with these companies we have identified three key types of interoperability between design and manufacture which we must accommodate. These are (i) interoperability between similar departments but across different organizations (ii) interoperability between
150
Z. Usman, R.I.M. Young,K.Case, J.A. Harding
different departments of the same organisation (iii) interoperability between different departments of different organisations. These are illustrated for different types of business in figure 2. Type (ii), especially between design and manufacture departments, is the most important to our work as it is particularly important for designers to understand the manufacturing consequences of their decisions.
Fig. 2. World Model Layers & Modes of Interoperability
3. A Manufacturing Foundation Ontology Approach to Interoperability While the concept of a foundation ontology is not new, with DOLCE, SUMO, OCHRE, OpenCyc, BFO [19]being examples, they tend to apply to very high, generic or “upper level” concepts which are not easily applied directly to the manufacturing domain. Some work has been done to work on Interoperability approaches [20], manufacturing ontologies [21] and semantic interoperability framework [22].Gunendran and Young[23] and Young et al [24] highlight important questions for sharing knowledg across PLC. Perhaps the most effective work is that of Borgo and Leito [25] who used concepts from foundation ontologies to build a manufacturing domain. In our approach we accept the use of upper level concepts where appropriate but believe that the range of concepts relevant to manufacturing is sufficiently broad as to warrant a manufacturing foundation ontology in its own right. Also, by targeting concepts in the
A Manufacturing Foundation Ontology for Product Life Cycle Interoperability
151
manufacturing domain, we believe that the concepts can be defined more tightly, which will aid in the evaluation of cross domain interoperability across manufacturing systems. Working across design and manufacture we can consider specific domain concepts for design and for manufacture. However we want to consider the foundation concepts which apply across both of these domains and across the full product lifecycle. We also recognise that the concepts which apply to automotive manufacture will not be totally in line with those for aerospace manufacture. We consider these as being different manufacturing “worlds” where the ability to represent knowledge of the particular “world” is critical. The actual design and manufacturing functions then would use “world” knowledge which has been constructed upon a formal foundation ontology. Hence we perceive of a knowledge framework as illustrated in Fig. 3. The MFO and the ‘worlds’ are meta modelling for interoperability though very specific worlds can be build from the framework. 3.1. Levels in a Manufacturing Foundation Ontology In our investigation of concepts for manufacture we have identified that some are specific to key areas in the lifecycle such as design, manufacturing, operation or disposal; some concepts are applicable to a product across all phases of the lifecycle and some concepts are generic to multiple product types which go well beyond the typically machined products with which we are mainly concerned. Illustrations of concepts from these three levels are described below and in particular the way in which some concepts apply at each level but with varying levels of specialisation. Re/Use of Foundation Ontology & World Models
Final Application & Re/Use
World Models Interoperable Knowledge Bases
How to Make/Design Company Specific Parts-World How To Make/Design PartsWorld How to Make/Design FeaturesDesign. Manufacture, Operation & Disposal Concepts
Foundation Ontology
Lifecycle Generic Concepts
Generic Concepts
Fig 3. The Manufacturing Foundation Ontology & Interoperability Framework
3.1.1 Generic Concept Level Generic concepts like activity, activity occurrence, feature, time point, dimension, tolerance, part, part family etc, are applicable across all types of product. Concepts from the generic level can then be specialised to Product Life Cycle (PLC) generic concepts and then to PLC specific concepts i.e. specific to either design or manufacture in our case.
152
Z. Usman, R.I.M. Young,K.Case, J.A. Harding
3.1.2 PLC Generic Concept Level Generic concepts are specialized into the PLC generic concepts which are applicable to any of the activities like design, manufacture, operate & dispose of the whole PLC but not outside it. Concepts like product feature, product part family, geometric dimensions, geometric tolerance, are specializations of generic concepts for the PLC generic concept level. 3.1.3 PLC Specific Concept Level The concepts at PLC specific level are specific to each activity of PLC and not outside that. Concepts for design and manufacturing domains are under development. Concepts like manufacturing feature and manufacturing part family are specialization of PLC generic concepts for manufacturing specific concepts. Similarly design feature and design part family are specialisations of PLC generic concepts for design specific concepts. Concepts specific to design or manufacture can only be used within their domain and not outside them. As the concepts are semantically enriched their semantic mediation, verification and mapping is ability is there when interoperating across different domains. 3.1.4 An Example of Specialisation through the Concept Levels This section uses the example of the concept of a feature to illustrate how a generic concept for feature can be progressively specialised and constrained into design feature and into various levels of manufacturing feature. This explains the 1st layer shown in Fig. 3. Fig 4 illustrates the taxonomic breakdown of a feature concept.
Fig 4. Screen captures of part of MFO describing Concept Specialization in MFO
A common logic [26] formalization of Fig 4 is explained below. First all the concepts like feature their various sub-classes and their associative relations are defined in IODE as follows. “:Prop” is used for introducing a concept in IODE. Declaration of a Concept In IODE :Prop Feature :Inst Type :sup ConcreteEntity :name "Feature" :rem "The MFO Generic Concept"
Definition of a Relation (binary) in IODE :Rel hasAttribute_of_Interest :Inst BinaryRel :Sig Feature Attribute_of_Interest :name "hasAttribute_of_Interest" :rem "hasAttribute_of_Interest ?feature ?AoI"
A Manufacturing Foundation Ontology for Product Life Cycle Interoperability
153
In a similar way all other concepts and relation are defined in KFL. The behaviour of a concept is partially controlled in its declaration by defining its type through “:Inst”, super classes or classes through “:sup”. The extensive rigour, integrity or semantic enrichment of concepts is done through the use of axioms or integrity constraints (IC). ICs are mainly of two types namely hard ICs and soft ICs which control the use of any concept by either disallowing the use of concept in case of hard IC or by giving a warning message in case of soft IC in case of the use of concepts in way which violates the ICs. The integrity constraints working behind the fig. 4 are explained next with an explanation of how to read them for a couple of initial constraints. (=> (and (Feature ?feature) ;If ?feature is a variable representing Feature ;and ?AoI is variable representing an Attribute of Interest (Attribute_of_Interest ?AoI)) (hasAttribute_of_Interest ?feature ?AoI) ) ;then ?feature has an Attribute_of_Interest. :IC hard "Every feature has an Attribute of Interest" (=> (and (Shape_Feature ?s_feature) ;If ?s_feature is a variable representing Shape_Feature (Shape ?shape)) ;and ?shape is a variable Shape (and (Feature ?s_feature) ;then ?s_feature is a Feature (hasShape ?s_feature ?shape) )) ;and ?s_feature has a ?shape :IC hard "Every Shape feature is a feature and has a shape" (=> (and (Product_Feature ?P_feature) (Product ?P) ) (and (Shape_Feature ?P_feature) (hasProduct ?P_feature ?P) )) :IC hard "Every Product feature is a Shape feature and has an associtaed product" (=> (and (Manufacturing_Feature ?M_feature) (Manufacturing_Process ?M_Process) ) (and (Product_Feature ?M_feature) (hasMfg_Pro ?M_feature ?M_Process) )) :IC hard "Every Manufacturing feature is a Product feature and has an associated Manufacturing Process" (=> (and (Design_Feature ?D_feature) (Function ?function) ) (and (Product_Feature ?D_feature) (hasFunction ?D_feature ?function) )) :IC hard "Every Design feature is a Product feature and has a associated function"
4. Discussion and Conclusion The manufacturing foundation ontology described focuses on the product lifecycle domain with specializations in design and manufacture. Parts designed using the proposed framework should benefit from the semantic rigour captured in the foundation ontology and hence provide an improved level of interoperability. The MFO is build in multiple layers with increasing levels of specialization which simplifies ontology building, concept selection and reuse. Three levels of
154
Z. Usman, R.I.M. Young,K.Case, J.A. Harding
specialisation have been defined to suit our needs but we anticipate that this would increase if the approach were applied across a wider area of application. An industrial exploration of the concepts for MFO is being undertaken at present in one of the partner aero-space companies. This will be used to develop and test the ideas against practical problems and requirements and provide an evidence for the use of MFO. This will lead to a more practical system and provide a basis for evaluating and analyzing the framework and the effectiveness of MFO in a real case scenario.
5. Acknowledgements This research work is funded by the Innovative Manufacturing and Construction Research Centre (IMCRC) in Loughborough University under the Interoperable Manufacturing Knowledge Systems (IMKS) project (IMCRC project 253). The authors would also to thank fellow researchers and colleagues in the IMKS project for their support and cooperation.
6. References [1] [2] [3] [4] [5] [6] [7]
[8] [9]
European Commission, Manufacture, (2004), A Vision for 2020, Assuring the Future of Manufacturing in Europe, Report of the High-level Group. Available from: http://www.manufuture.org/documents/manufuture_vision_en[1].pdf Johanson, U., Industry, Trade and Services (2008), eurostat-statistics in focus, 37/2008. Availabel from: http://epp.eurostat.ec.europa.eu/cache/ITY_OFFPUB/KSSF-08-037/EN/KS-SF-08-037-EN.PDF Trade policy review report by European communities, (2009), World Trade Organization-Trade Policy Review Body, page 16. Available from: http://www.wto.org/english/tratop_e/tpr_e/g214_e.doc ICT for Manufacturing, (2005), Report of Meeting with Group of Representatives of Five Expert Panels,15 March 2005 in Brussels Ray S.R., Jones A.T. (2003) Manufacturing interoperability. Concurrent Engineering, Enhanced Interoperable Systems. Proceedings of the 10th ISPE International Conference, Madeira Island, Portugal: 535–540 Brunnermeier, S. B. and Martin, S. A., (1999), Interoperability Cost Analysis of the U.S. Automotive Supply Chain, Technical report, NIST, Research Triangel Institute, Planning Report- 99-1. Tan, P, Madnick, S.E, Tan, K.L. (2005) Context Mediation in the Semantic Web: Handling OWL Ontology and Data Disparity Through Context Interchange. In: Bussler, C.J., Tannen, V., Fundulaki, I. (eds.) SWDB (2004), Springer, Heidelberg, LNCS, vol. 3372, pp. 140–154. Gruber, T., (1993). Towards principles for the design of ontologies used for knowledge sharing”, International Journal of Human-Computer Studies .Vol. 43(5/6),pp.907-928. Uschold, M. Gruninger, M, (1996), Ontologies: Principles methods and applications, The Knowledge Engineering Review 11 (2) (1996) 93–155.
A Manufacturing Foundation Ontology for Product Life Cycle Interoperability 155 [10] Guarino, N., (1997), Understanding, building and using ontologies, International Journal .Human-Computer Studies,46 , 293 – 310. [11] Borst, W., N., Construction of Engineering Ontologies, (1997), PhD Thesis, University of Tweenty, Enschede, NL––Centre for Telematica and Information Technology. [12] Studer, R, Benjamins, V.R, Fensel, D. (1998) Knowledge engineering: principles and methods, Data and Knowledge Engineering 25 161–19 [13] Schlenoff, C., Gruninger, M., Tissot, F., Valois, J., et, al (2000)"The Process Specification Language (PSL): Overview and Version 1.0 Specification," NISTIR 6459, National Institute of Standards and Technology, Gaithersburg, MD. [14] Roche, C., (2000), Corporate ontologies and concurrent engineering, Journal of Materials Processing Technology, 107, 187-193 [15] Natalya F. Noy and Deborah L. McGuinness, (2002), “Ontology Development 101: A Guide to Creating Your First Ontology”, Stanford University, Stanford, CA. [16] Blomqvist, E., O¨hgren, A. (2008), ‘Constructing an enterprise ontology for an automotive supplier’, Engineering Applications of Artificial Intelligence 21, 386–397 [17] ISO 18629-1, ISO TC184/SC4/JWG8, (2004), Industrial Automation System and Integration—Process Specification Language: Part 1. Overview and Basic Principles. [18] ISO/DIS 10303-224.3 (2003) Product data representation and exchange: Application protocol: Mechanical product definition for process planning using machining [19] Oberle, Daniel, et al. (2007), "DOLCE Ergo SUMO: On Foundational and Domain Models in the SmartWeb Integrated Ontology (SWIntO)." Web Semantics: Science, Services and Agents on the World Wide Web 5.3: 156-74. [20] ISO (CEN/ISO)11354 ,V8.3 (2008), Requirements for establishing manufacturing enterprise process interoperability, PART I:Framework for Enterprise Interoperability. [21] LAGOS, N. and 'SETCHI, R.M.'., A manufacturing Ontology for e-learning. [22] Chungoora, N. and Young, R.I.M., (2009) "A Semantic Interoperability Framework for Manufacturing Knowledge Sharing", Submitted for the International Conference on Knowledge Management and Information Sharing (KMIS), Madeira, Portugal, 6th - 8th October 2009. [23] Gunendran, A.G., and Young, R., I., M., (2008), Methods for the Capture of Manufacture Best Practice in Product Lifecycle Management, International Conference on Product Lifecycle Management. [24] Young, R.I.M, Gunendran, A.G, Cutting-Decelle, A.F, Gruninger, M, (2007), Manufacturing knowledge sharing in PLM: a progression towards the use of heavy weight ontologies, International Journal of Production Research, Vol. 45, No. 7, 1 April, 1505–1519 [25] Borgo, S, Leitão, P., (2007), Foundations for a core ontology of manufacturing, 1Laboratory for Applied Ontology, ISTC-CNR, via Solteri 38,38100 Trento, 2Polytechnic Institute of Bragança, Quinta Sta Apolónia, Apartado, Bragança, Portugal.1134, 5301-857 [26] ISO/IEC-24707 (2007), Information technology — Common Logic (CL): a framework for a family of logic based languages, International Standard, First edition 2007-10-01.
A Semantic Mediator for Data Integration in Autonomous Logistics Processes Karl Hribernik1, Christoph Kramer1, Carl Hans1, Klaus-Dieter Thoben1 1
BIBA - Bremer Institut für Produktion und Logistik GmbH Hochschulring 20 28359Bremen
Abstract. Autonomous control in logistic systems is characterized by the ability of logistic objects to process information, to render and to execute decisions on their own. This paper investigates whether the concept of the semantic mediator is applicable to the data integration problems arising from an application scenario of autonomous control in the transport logistics sector. Initially, characteristics of autonomous logistics processes are presented, highlighting the need for decentral data storage in such a paradigma. Subsequently, approaches towards data integration are examined. An application scenario exemplifying autonomous control in the field of transport logistics is presented and analysed, on the basis of which a concept, technical architecture and prototypical implementation of a semantic mediator is developed and described. A critical appraisal of the semantic mediator in the context of autonomous logistics processes concludes the paper, along with an outlook towards ongoing and future work. Keywords: semantic mediator, semantics, ontologies, data integration, autonomous logistics processes
1. Introduction Autonomous control in logistic systems is characterized by the ability of logistic objects to process information, to render and to execute decisions on their own [1]. The requirements set by complex logistics systems towards the integration of data regarding the individual entities within them prove immensely challenging. In order to implement complex behaviour with regards to autonomous control, dynamism, reactivity and mobility, these entities, including objects such as cargo, transit equipment and transportation systems but also software systems such as disposition, Enterprise Resource Planning (ERP) or Warehouse Management Systems (WMS) require the development of innovative concepts for the description of and access to data. [2]
158
K.A. Hribernik, C. Kramer, C. Hans and K.-D. Thoben
2. Related Work The following sections review related work relevant to data integration in autonomous logistics processes. First of all, an understanding of the term “autonomous logistics processes” is developed and the necessary properties of supporting information systems to support such processes are identified. Subsequently, data integration approaches are reviewed in order to identify one which provides adequate support for the properties identified in the first step. 2.1. Characteristics of Autonomous Logistics Processes According to [1], “Autonomous Control in logistic systems is characterized by the ability of logistic objects to process information, to render and to execute decisions on their own.” They furthermore define logistics objects in this context as “material items (e.g. part, machine and conveyor) or immaterial items (e.g. production order) of a networked logistic system, which have the ability to interact with other logistic objects of the considered system.” In [3], the former are further differentiated as commodities and all types of resources and whilst constraining the immaterial logistics objects to orders. In [4], a catalogue of criteria for autonomous cooperating processes is suggested. Within this catalogue, three criteria explicitly address the “information system” layer, as illustrated in Fig. 1 below. Specifically, these criteria deal with the properties of data storage, data processing and the system’s interaction ability. The first two criteria are directly related to the problem of data integration. The properties of these criteria make apparent that the less central the data storage and processing of an information system is, the higher the level of autonomous control is. The third criterion, interaction ability, relates implicitly to the data integration problem, in that the interaction ability of the information system in question is based upon its ability to access and process data stored according to the initial two criteria.
Fig. 1. Information System Layer Criteria for Autonomous Cooperating Processes [4]
A Semantic Mediator for Data Integration in Autonomous Logistics Processes
159
Consequently, an IT system can be said to contribute to the autonomous control of a logistics system if it provides support for information processing and decisionmaking on the part of logistics objects, both material and immaterial. Furthermore, the information system is required to exhibit the properties data storage, data processing and interaction ability with respect to these types of logistics objects. This paper concentrates on the first of the three properties – data storage – and investigates a semantic mediator can be applied to support a decentral approach to the storage of autonomous logistics data. 2.2. Data Integration Approaches The diversity of systems involved in complex, autonomous logistics processes defines challenging requirements towards an approach to data integration in this field. The variety of different applications, data sources, exchange formats and transport protocols demand a high level of flexibility and scalability. To address these challenges, the specific requirements complex logistics systems exhibit need to be considered. A number of different, traditional solutions to data integration may be taken into account, foremost amongst these tightly coupled, loosely coupled and object-oriented approaches [5]. Whilst a tightly coupled approach can quickly be dismissed on grounds of its inflexibility, loosely coupled and object-oriented approaches cannot be adopted without critical analysis. An object oriented approach generally provides good mechanisms for avoiding integration conflicts. However, when considering this approach, one must take into account that a single canonical model is required to describe the entire data model, which clearly restricts its flexibility and scalability. Each time a new stakeholder or data source enters the logistics system, the model needs to be extended. Depending on the dynamics of the logistics system, this may or may not be a disqualifying factor with regards to this approach. As the fluctuation of data sources, stake holders and systems in a complex logistics system with any degree of autonomous control can be assumed to be high, an object-oriented approach to data integration is likely to be unsuitable. A loosely coupled approach requires detailed knowledge of each of the heterogeneous data sources to be able to be successfully employed. With regards to complex logistics systems, further analysis is required to determine whether this is feasible or not. The possibility of requiring highly flexible, and thus possibly not always pre-determinable, context data, for example from sensor networks, may prove to be an argument against this approach. Besides the aforementioned traditional approaches to data integration, a number of predominantly semantic approaches remain to be taken into account. Here, the main concepts constituting the architecture of such data integration systems are mediators [6]. In this approach, both syntactic and semantic descriptions of the data to be integrated are applied. The semantic mediator is capable of extracting knowledge regarding the data structures of the underlying data sources and subsequently transforming, decomposing and recomposing data requests according to that knowledge. The mediator relies on semantic descriptions of the data sources. In the case of autonomous logistics processes, this implies a wholly
160
K.A. Hribernik, C. Kramer, C. Hans and K.-D. Thoben
semantic modeling of the relevant logistics information and data across the distributed, heterogeneous sources, for which a number of approaches, such as ontologies, may be chosen. Here, extensive research is required to determine whether such semantic descriptions of logistics data are feasible and adequate to address the requirements of autonomous logistics processes. However, the application of the semantic mediator to the problem area currently offers the most promising solution candidate — the following paragraphs attempt to sketch a technical concept to the problem on that basis and evaluate it through the appraisal of a prototypical implementation within a defined application scenario.
3. Research Approach The aim of the research presented in this paper is to develop a concept for the integration of data in autonomous logistics processes, specifically in the field of transport logistics. The semantic mediator was identified as a promising concept based on the analyis of related work outlined above. In order to achieve a better understanding of the requirements autonomous control in transport logistics processes poses towards semantic mediation, an application scenario was defined and analysed. The scenario selected is based on simulation experiments used to demonstrate the principles of autonomous control using multi-agent systems [7]. It illustrates the application of autonomous control for the transport of fresh fruit products through Europe, taking into account the use of sensors [8] and shelf-life prediction [9] in combination with a multi-agent based system [10] to monitor and control the relevant logistics processes. Analysis of the scenario focused mainly on identifying the agents’ data requirements in the autonomous logistics processes, and by what means that data may be communicated, taking standard data exchange formats and interfaces commonly used in the field of transport logistics into account. The following section describes the application scenario in detail. 3.1. Application Scenario This scenario illustrates the application’s processes as a story-board exemplifying one possible simulation run. The application scenario’s processes are illustrated in a BPMN (Business Process Modeling Notation) diagram in Fig. 2 below. To begin with, an order is placed with the fruit producer in Poznań, Poland for e.g. a crate of blueberries to be delivered to a restaurant in Paris, France. The order is placed electronically as a business-to-business transaction, from the customer’s ERP system to an order management agent, which identifies the goods to be transported and initializes a shipping agent to start the autonomous transport logistics processes. The shipping agent’s initial task is to identify a suitable means of transport for the delivery of the fruit it is responsible for. It does this by making use of the services of a transport brokerage agency. This agency provides an electronic market where freight forwarders can publish details about their available transport capacities, including their current routes, possible delivery times, cooling capabilities, special equipment such as temperature sensors, and so on. The
A Semantic Mediator for Data Integration in Autonomous Logistics Processes
161
shipping agent can thus discover which means of transport come into question for the route to Paris, taking into account the requirements resulting from the type of goods to be transported. Fresh fruits require cooling and temperature monitoring and need to be delivered within a defined time frame. The shipping agent begins negotiations with the respective transport agents and chooses and books the most appropriate one. The selection is made the agent on the basis of a number of weighted criteria such as pricing, delivery time guarantees, and quality of service.
Freight
Means of transport
Transport discovery
Sequence Flow Message Flow
Shipping agent
Sensor check
Traffic warnings check
Rerouting
Monitor environment values during the journey
Discover cold storage
+
Carrier
+
Cold storage
Sensors
Fig. 2. BPMN-Diagram of the Application Scenario
Once the selected truck has picked the fruits up, it is ready to begin the delivery process. The shipping agent first contacts the agent representing the sensor network in the truck. It ensures the required sensors are present and operating satisfactorily. Having passed the sensor check, the shipping agent arranges for the deployment of a dedicated shelf life monitoring agent, developed and preconfigured by the food producer [11] which automatically connects to the sensor net. The shipping agent then acknowledges that everything is satisfactory and delivery may commence. The sensor network continuously monitors the shipping conditions and after some time detects an increase in temperature in the front part of the reefer where the crates with berries are located. The monitoring agent evaluates the situation as critical. Its shelf life prediction based on the sensor readings suggest that unacceptable degradation of fruit quality will occur if the current transport plan is not changed. It contacts the shipping agent in order to find a replacement means of transport at a nearby transshipping point. The shipping agent renegotiates transport according to the process outlined above. A new means of transport is discovered and the handover negotiated. Alternatively, if no suitable transport can be found, the shipping agent may attempt to find a temporary storage facility providing cooling and temperature monitoring facilities. The process for discovering and negotiating warehouse storage space is analogous to that for acquiring a means of transport. The above autonomous logistics processes iterate until the goods are delivered at the customer’s delivery address.
162
K.A. Hribernik, C. Kramer, C. Hans and K.-D. Thoben
4. Findings 4.1. Scenario Analysis On the basis of the application scenario, the data integration requirements were identified by first modeling the autonomous logistics processes in BPMN exhibited by the scenario (cf. Fig. 2), and then modeling and analyzing the communication which takes place between the individual actors. The next step taken was to map the communication between the individual actors to messages and events represented by standard data exchange formats used in transport logistics. The selection of exchange formats was guided by a market study which identified the most prominent exchange formats used in IT systems supporting transport logistics. Consequently, business-to-business communications and agent interactions were mapped to EDIFACT (Electronic Data Interchange For Administration, Commerce and Transport) EANCOM (EAN + Communication) messages whilst information regarding the tracking and tracing of the material flow through the scenario were mapped to EPCIS (Electronic Product Code Information Service) events. 4.2. System architecture
Agent
Agent
Agent Mediator QueryInterpreter
Legend Agent Communication Data Exchange
WrapperDisposer
Raw Data Exchange (in DBMS-Format)
EANCOMWrapper MessageCreator
MessageProcessor
EPCISWrapper EventCreator
EventProcessor
EPCIS Repository DB
DB
Fig. 3. Mediator Architecture Definition
The proposed system architecture illustrated in Fig. 3 follows the traditional pattern of a semantic mediator - besides the actual mediator component, which possesses a global ontology of the autonomous logistics processes of the application scenario, the wrapper components each contain extension ontologies which fully formalize
A Semantic Mediator for Data Integration in Autonomous Logistics Processes
163
the data sources they are responsible for as semantic descriptions. Heterogeneity conflicts [21] are solved either by the mediator component itself or by the respective wrapper, depending on the type of conflict. Due to the application scenario and the selected data exchange formats only very few of the conflicts as described by [21] occur. 4.3. Semantic Data Descriptions: Ontology Specifications The description of the application domain as well as the objects and data in this domain were implemented as a global ontology. The system, however, is designed to support the use of multiple ontologies in order to leverage modular flexibility and scalability of the mediator approach in further applications. The Web Ontology Language (OWL-DL) [16] was used for the specification of the ontology which describes the individual data exchange formats. OWL-DL was chosen for three reasons: first of all, it is used in the multi-agent system for the description of the domain of autonomous controlled logistics. Secondly, it was judged to be adequately expressive to cover the semantic description of both the standard exchange formats used in transport logistics and the overarching concepts of autonomous logistics processes. Finally, a number of Java libraries and reasoners are readily available for OWL-DL, which was expected to significantly accelerate the development of a prototypical implementation. The ontology used is a critical success factor of any semantic mediator. It has to reflect all the characteristics of the application domain and simultaneously has to be as simple and comprehensible as possible. Many existing onotologies may be taken into consideration for the semantic description of the entities in the given transport logistics scenario, such as those used in the fields of product lifecycle and data management as exemplified by [18], [19] or [20]. However, none of these truly reflect the syntax and semantics of autonomous logistics processes whilst encompassing the syntax and semantics of standard logistics data exchange formats. Consequently, as a first step, a new ontology was designed based on both the application scenario and the top-level ontology of the multi-agent system which describes basic concepts of autonomous logistics processes. It can be extended can by incorporating additional ontologies into the system. By using the OWL-DL features “owl:equivalentClass” and “owl:equivalentProperty”, the possibility for linking the ontology to other existing ontologies is available. 4.4. Querying the Semantic Mediator The query language “SPARQL” [12] is used as the query language at the query interface of the system. It was specifically developed for querying ontologies and thus provides an adequate basis for queries to the semantic mediator. However, SPARQL only offers the possibility to query the system but not write to it. However, SPARQL alone doesn’t fulfill all of the requirements, because agents representing autonomous objects also need to be able to create messages and data. To extend the functionality to support bidirectional queries, the “SPARQL Update” [13] language was used to extend the SPARQL query
164
K.A. Hribernik, C. Kramer, C. Hans and K.-D. Thoben
language. This allows for the editing of ontologies with a similar syntax to SPARQL. A combination of both languages was specified and prototypically implemented as the query language in of the semantic mediator. 4.5. Data Transformation in the Wrappers The wrappers query data from the respective data sources and transform it via an internal format in order to enable the processing of data from heterogeneous data sources and formats. The transformation is carried out within the wrappers and is transparent to the actual mediator component. This allows for a complete abstraction from the data sources. Transformation in the wrappers is rule-based and described and implemented using to the business rule management system “Drools” [14] (Drools - Business Logic Integration Platform). The use of Drools offers the possibility to react more quickly and flexibly to modifications to individual data sources. Should a change need to be made, only the rule files need to be updated. Modifications to the source code of the wrappers with subsequent recompilation and deployment can be avoided in this way. 4.6. System Test and Prototypical Implementation In order to test the semantic mediator with the application scenario described above, all of the mediator components were prototypically implemented. The data sources described in the application scenario were also implemented. A repository was set up for both EPCIS and EANCOM. The Fosstrak EPCIS repository [15] was used to query and capture the EPCIS events. A minimal EANCOM messaging implementation was developed to relay the respective messages. These repositories formed the basis for the communication. Every message or event created is stored in the corresponding repository to support the validation of the system.
5. Conclusions and Outlook Validation of the prototypical implementation against the application scenario demonstrated the applicability of the concept of the semantic mediator in the field of autonomous logistics processes. The semantic mediator proved capable of fulfilling the bidirectional data integration requirements set by the application scenario. For this scenario, the semantic mediator supports a decentral approach to the storage of autonomous logistics data , consequently fulfilling the first criterion of the “information system” layer for autonomous cooperating processes [4] and thus contributing to the potential for autonomous control in the transport logistics sector. From a more practical point of view, one issue is currently in the focus of current work. The extended SPARQL query interface of the semantic mediator is difficult to integrate with existing systems. A loosely-coupled approach is being
A Semantic Mediator for Data Integration in Autonomous Logistics Processes
165
investigated which aims at providing a generic, service-based interface towards the semantic mediator which can be easily accessed both by enterprise systems and autonomous logistics objects represented, for example, by software agents. Also, it remains to be shown that the concept for a semantic mediator presented in this paper is adequate for more complex scenarios in autonomous logistics. First of all, the data expressed by the standard data exchange formats EPCIS and EDIFACT EANCOM are, by design, largely disjunct. The former deals mainly with tracking and tracing the logistics material flow whilst the latter is concerned with communicating business-to-business messages. Consequently, the potential for heterogeneity conflicts in this scenario is quite limited. Future work will analyse whether the presented concept is suitable for more complex scenarios involving more data sources with a higher potential for conflict. Beyond the current focus on the domain of autonomous control in transport logistics, future work will be directed towards expanding the vocabulary of the mediator into other logistics domains, such as production and reverse logistics. This implies investigating existing ontologies in these areas and how they may be integrated into the current development. Here, one promising approach may be to adopt an ontology from the domain of product lifecycle management in order to link the individual autonomous transport logistics processes into the overall product lifecycle context.A further aspect to be taken into consideration in future work is that of the integration of dynamic data sources. More demanding scenarios of autonomous control in logistics rely heavily on the availability of reliable, realtime data from, for example, sensor networks. Whether and how the presented semantic mediator can be successfully applied to integrating such data will be the focus of future research.
6. Acknowledgements This research was supported by the German Research Foundation (DFG) as part of the Collaborative Research Centre 637 “Autonomous Cooperating Logistic Processes”.
7. References [1]
[2]
[3]
Böse, Felix, and Katja Windt. “Catalogue of Criteria for Autonomous Control in Logistics.” In Understanding Autonomous Cooperation and Control in Logistics - The Impact on Management, Information and Communication and Material Flow, by Michael Hülsmann and Katja Windt. Berlin:,Springer, 2007. 57-72 Hans, Carl, Karl Hribernik, and Klaus-Dieter Thoben. “An Approach for the Integration of Data within Complex Logistics Systems.” LDIC2007 Dynamics in Logistics: First International Conference. Proceedings. Heidelberg: Springer, 2007. 381-389. Scholz-Reiter, Bernd, Jan Kolditz, and Thorsten Hildebrandt. “Specifying adaptive business processes within the production logistics domain – a new modelling concept and its challenges.” In Understanding Autonomous Cooperation & Control in Logistics – The Impact on Management, Information and Communication and
166
[4]
[5] [6] [7]
[8]
[9] [10]
[11] [12] [13] [14]
[15] [16] [17] [18]
K.A. Hribernik, C. Kramer, C. Hans and K.-D. Thoben Material Flow, by Martin Hülsmann and Katja Windt, 275-301. Berlin: Springer, 2007. Windt, Katja, Felix Böse, and Thorsten Phillipp. "Criteria and Application of Autonomous Cooperating Logistic Processes." Proceedings of the 3rd International Conference on Manufacturing Research - Advances in Manufacturing Technology and Management. Cranfield, 2005. Wache, H. (2003). Semantische Mediation für heterogene Informationsquellen. Akademische V.-G. Aka . Ullman, J.D.: Information integration using logical views. In F.N. Afrati and P. Kolaitis, editors, Proceedings of the 6th International Conference on Database Theory (ICDT’97), 1997. Jedermann, R., Gehrke, J. D., Becker, M., Behrens, C., Morales Kluge, E., Herzog, O., et al. (2007). Transport Scenario for the Intelligent Container. In M. Hülsmann, & K. Windt, Understanding Autonomous Cooperation & Control in Logistics. The Impact on Management, Information and Communication and Material Flow (pp. 393-404). Berlin: Springer. Jedermann, R.; Behrens, C.; Laur, R.; Lang, W.: Intelligent containers and sensor networks, Approaches to apply autonomous cooperation on systems with limited resources. In: Hülsmann, M.; Windt, K. (eds.): Understanding Autonomous Cooperation & Control in Logistics – The Impact on Management, Information and Communication and Material Flow. Springer, Berlin, 2007, pp. 365-392 Jedermann, R.; Edmond, J.P.; Lang, W.: Shelf life prediction by intelligent RFID. In: Haasis, H.D.; Kreowski, H.J.; Scholz-Reiter, B. (eds.): Dynamics in Logistics. First International Conference, LDIC 2007, Springer, Berlin Heidelberg, 2008, pp. 231-240 Gehrke, J.D.; Ober-Blöbaum, C.: Multiagent-based Logistics Simulation with PlaSMA. In: Koschke, R.; Herzog, O.; Rödiger, K.-H.; Ronthaler, M. (eds.): Informatik 2007 - Informatik trifft Logistik, Band 1. Beiträge der 37. Jahrestagung der Gesellschaft für Informatik e.V. (GI), GI, Bonn, 2007, pp. 416-419 R. Jedermann, C. Behrens, D. Westphal, W. Lang, Applying autonomous sensor systems in logistics; Combining Sensor Networks, RFIDs and Software Agents, Sensors and Actuators A (Physical) 132 (1), 2006, pp. 370-375. Prud'hommeaux, E., & Seaborne, A. (2008, Januar 15). SPARQL Query Language for RDF. Retrieved 07 15, 2009, from http://www.w3.org/TR/rdf-sparql-query/ Seaborne, A., Manjunath, G., Bizer, C., Breslin, J., Das, S., Harris, S., et al. (2008, July 15). SPARQL Update. A language for updating RDF graphs. Retrieved 07 28, 2009, from http://www.w3.org/Submission/SPARQL-Update/ Drools Community Documentation. Drools Introduction and General User Guide 5.0.1 Final. JBoss Enterprise, 2009. Retrieved 07.12.09 from http://downloads.jboss.com/drools/docs/5.0.1.26597.FINAL/droolsintroduction/html_single/index.html Roduner, C., Steybe, M.: Fosstrak EPCIS. ETH Zurich & University St. Gallen. Retrieved 07.12.09 from http://www.fosstrak.org/epcis/index.html Smith, M. K., Welty, C., & McGuinness, D. L. (2004, Februar 10). OWL Web Ontology Language Guide. Retrieved 07 15, 2009, from http://www.w3.org/TR/owlguide/ Wiederhold, G. (1992). Mediators in the Architecture of Future Information Systems. Computer , pp. 38-49. Terzi, S. (2005). Elements of Product Lifecycle Management: Definitions, Open Issues and Reference Models. PhD – University Henri Poincaré Nancy 1 and Politecnico di Milano, May
A Semantic Mediator for Data Integration in Autonomous Logistics Processes
167
[19] Tursi, A. (2009). Ontology-approach for product-driven interoperability of enterprise production systems. PhD - University Henri Poincaré Nancy 1 and Politecnico die Bari, November [20] Jeongsoo Lee, Heekwon Chae, Cheol-Han Kim, Kwangsoo Kim. (2009). Design of product ontology architecture for collaborative enterprises. In Expert Systems with Applications, Volume 36, Issue 2, Part1, pp. 2300-2309 [21] Wache, H., Vögele, T., Visser, U., Stuckenschmidt, H., Schuster, G., Neumann, H., Hübner, S. (2001). Ontology-Based Integration of Information – A Survey of Existing Approaches
An Ontology Proposal for Resilient Multi-plant Networks Rubén Darío Franco1, Guillermo Prats1, Rubén de Juan-Marín2 1 2
Centro de Investigación, Gestión e Ingeniería de Producción Univ. Politécnica de Valencia; 46022 Valencia, Spain Instituto Tecnológico de Informática Univ. Politécnica de Valencia; 46022 Valencia, Spain
Abstract. This paper presents an ontology proposal for the REMPLANET FP7 project which aims at developing methods, guidelines and tools for the implementation of the Resilient Multi-Plant Networks in non-hierarchical manufacturing networks, characterized by noncentralized decision making. Due to structural heterogeneity of REMPLANET integration scenarios, an ontological approach seems to be a first key challenge to be addressed. Consequently, one of the main contributions of this paper is to provide an initial ontological approach, intended to harmonize domain concepts and their relationships. Keywords: Ontology engineering, Resilient multi-plant networks, Interoperability.
1. Introduction Nowadays, collaboration among organizations is increasing and becoming a critical issue in profiting from ever-evolving market needs. In manufacturing and distribution networks, the traditional concept of static Supply Chains is changing towards a broader concept where they are defined as the operations management of heterogeneous, dynamic and, geographically distributed partners. This new environment is making enterprises changing the way they manage their trading relationships. Interoperability is a critical issue to take into consideration when such collaboration needs appear due to the importance of information exchange and distributed coordination needs. The European Project REMPLANET is intended to create methods and tools in supporting resilient organizational models. In doing so, a multi-disciplinary approach will be followed and defining a unified and commonly agreed understanding of main
170
D. Franco, G. Prats, R. de Juan-Marín
concepts, and their relationships, it is considered a first critical step for project partners. Collaboration among project members is crucial to achieve REMPLANET objectives. Entities from several countries will participate in the project; it is necessary to define in a unique way, different concepts that will be used in the domain of the project, in order to facilitate communication between them. Data interoperability between members will be essential for the success of the project objectives. This data interoperability will facilitate understanding between members of different countries. This paper presents an ontology proposal, defined as a unique form of representing knowledge applied in various domains, in order to provide a global view of the project scenario. Its main objective is to unify REMPLANET concepts and its relations for all the partners involved in the project. In this way, interoperability problems identified in an inter-operational environment such as conceptual barriers could be avoided. This ontology will facilitate partners to understand how concepts are interrelated and it also will facilitate information sharing. The document has been structured as follows. In Section 2, REMPLANET Project is introduced. In Section 3, a short introduction to basic concepts and definitions are given. In Section 4, ontology for the REMPLANET Project is described. Section 5, conclusion and next steps are envisioned.
2. The REMPLANET Project REMPLANET Project is funded by the European Union by the Seventh Framework Programme. The main concept of the project is to develop methods, guidelines and tools for the implementation of the Resilient Multi-Plant Networks Model in nonhierarchical manufacturing networks, characterized by non-centralized decision making. Resilience is defined as the capacity to adapt to major internal disruptions. The project defines the concept of a resilient organization as the capacity to respond rapidly to unforeseen change, even chaotic disruption. It is the ability to bounce back — and, in fact, to bounce forward — with speed, determination and precision. A resilient organization effectively aligns its strategy, operations, management systems, governance structure, and decision-support capabilities so that it can uncover and adjust to continually changing risks, endure disruptions to its primary earnings drivers, and create advantages over less adaptive competitors. A Resilient Organization can be understood from two points of view: operational resilience and strategic resilience. Operational resilience is defined as the ability to respond to the ups and downs of the business cycle or to quickly rebalance product-service mix, processes, and the supply chain, by bolstering enterprise agility and flexibility in the face of changing environments. On the other hand, strategic resilience is defined as the ability to dynamically reinvent business models and strategies as circumstances change. It is not about responding to a one-time crisis, or just having a flexible supply chain. It is about continuously anticipating and adjusting to discontinuities that can permanently impair the value proposition of a core business. Strategic resilience refers, therefore,
An Ontology Proposal for Resilient Multi-plant Networks
171
to a capacity for continuous reconstruction. It requires innovation with respect to those organizational values, processes, and behaviors that systematically favor perpetuation over innovation, renewal being the natural consequence of an organization’s innate strategic resilience. In terms of operational resilience, a key issue faced by organizations today is the challenge to deliver the products matching the needs of individual customers, in different geographical markets, at any time, and preferably individually customized, as cheaply and as quickly as possible. The mass customization strategy has been suggested as a way to address the challenge of providing individual products with mass production efficiency. On the other hand, in terms of strategic resilience, the project will take the perspective of open innovation [1]. It has been shown that both the efficiency and the effectiveness of innovation can be increased dramatically when innovation is not seen as a closed process conducted with one form, but as an open activity within a network of loosely-coupled actors, including the users of the product or service.
3. Basic Concepts and Definitions Information exchange needs of REMPLANET actors will be critical to achieve resilience objectives. Taking into consideration that the REMPLANET integration scenarios will be geographically distributed and socio-cultural divergences may appear, removing such conceptual barriers will be an important problem to deal with. In doing so, ontologies have been identified in IDEAS [2] as one of the three domains that tackle interoperability problems. As stated before, the main objective of this paper is to provide an ontology proposal in order to avoid data interoperability problems between REMPLANET partners. 3.1. Interoperability Interoperability goes far beyond the simple technical problems of computer hardware and software, but encompasses the broad but precise identification of barriers not only concern data and service but also process and business as well [3]. In the context of Multi-Plant Networks, interoperability between partners plays an important role in order to achieve success. Interoperability is defined as the ability of information systems to operate in conjunction with each other encompassing communication protocols, hardware, software, application, and data compatibility layers [4]. Other authors state that an interoperability problem appears when two or more heterogeneous resources are put together. Interoperability per se is the paradigm where an interoperability problem occurs [5]. Finally, definitions of interoperability have been reviewed in [6], [7]. There have been identified a group of barriers that do not allow interoperability among enterprises. Those barriers appear in diverse enterprise levels. Those can be understood as incompatibilities that obstruct information sharing and prevent from exchanging services. Barriers are common to all enterprises whatever the sector of activities and size. Developing interoperability means to develop knowledge and solutions to remove incompatibilities [8].
172
D. Franco, G. Prats, R. de Juan-Marín
Fig. 1 shows the framework that was developed within the frame of INTEROP Network of Excellence in order to better understand the problem and the vision of interoperability. As showed, there have been identified three groups of interoperability barriers [9]: • Conceptual barriers, • Technological barriers and, • Organizational barriers.
Fig. 1. Enterprise interoperability framework (three basic dimensions)
Generally, conceptual barriers are defined as syntactic and semantic difference of information exchanged. In order to solve conceptual problems, a solution could be to develop an ontology in order to define terminology that will be used between partners. This paper will center its efforts in solving conceptual barriers for the REMPLANET project. 3.2. Ontology As mentioned above, interoperability barriers can be divided in three main groups. One solution identified in the literature to solve conceptual barriers, is to develop an ontology for the domain being considered. Ontology is defined as a unique form of representing knowledge applied in various domains. An ontology is a formal, explicit specification of a shared conceptualization [10]. The main advantage for having such formal specification is to facilitate the knowledge sharing and re-use among the various parties interested in that particular domain of knowledge. In the context of a European Project, having a set of standardized ontology will enhance understanding between partners. Using the ontology for defining project concepts will result in a reusable, easy to integrate knowledge bases.
An Ontology Proposal for Resilient Multi-plant Networks
173
3..3 Ontology Construction Methodology The Ontology was developed using Protégé software. Protégé is a free open-source software tool that was developed at Stanford University for building Ontologies and knowledge based systems. To define the domain and scope of the ontology, several basic questions have been answered: • What is the domain that the ontology will cover? • For what we are going to use the ontology? • For what types of questions the information in the ontology should provide answers? • Who will use and maintain the ontology? One of the ways to determine the scope of the ontology is to sketch a list of questions that a knowledge base based on the ontology should be able to answer, competency questions [11]. To develop the Ontology, a list of terms was written down. Initially, it was important to get a comprehensive list of terms without worrying about overlap between concepts they represent, relations among the terms, or any properties that the concepts may have, or whether the concepts are classes or slots. The next two steps were developing the class hierarchy and defining properties of concepts. There are several possible approaches in developing a class hierarchy [12]: topdown, bottom-up and a combination of both. The ontology was built by defining classes, subclasses, properties, and instances representing REMPLANET environment using the combination process.
4. REMPLANET Ontology Proposal In dynamic environments, where conditions are constantly changing, rejecting Business Opportunities due to the lack of flexibility could be the end of the business. To avoid this scenario, REMPLANET will develop methods, guidelines and tools for the implementation of Resilient Multi-Plant Networks Model in non-hierarchical manufacturing networks, characterized by non-centralized decision making. Next, the ontology proposal is showed and a briefly description is given. The ontology has been divided into three simpler views in order to facilitate understanding, resilient organization, members and ITC Platform. Fig. 3 shows the view of a Resilient Organization. It can be formed by the company network, the group network in case the company is a member of a group, and required external networks without current links with the company, for the new product-service/processes collaborative co-design materialization. From an organizational point of view, the “resilience” concept has two perspectives: operational resilience and strategic resilience.
174
D. Franco, G. Prats, R. de Juan-Marín
All members of REMPLANET Scenario will be connected to an ICT Platform with the aim of react to business opportunities faster than competence and to support automated process.
Fig. 2. Resilient Organization View
Each individual network can be formed by several organizations forming its own supply chain. These members can be Manufacturing Plants, Distributor companies, Logistic Operators among others. Organizations have to be resilient in the meaning that has to adapt its capabilities not only in episodic or crisis-driven, creating more advantages than its competitors. Attending to this flexibility, more customers and business opportunities will be satisfied. Each member could play different roles in the REMPLANET scenario such, coordinator, partner and supplier. Fig. 4 shows relation between members and the resilient organization.
Fig. 3. Members of REMPLANET Scenario
REMPLANET Scenario will offer to its network the possibility to use an ICT Platform in order to facilitate communication. This platform is composed of various modules, EBPM (Extended Business Process Management), SOP (Service Oriented
An Ontology Proposal for Resilient Multi-plant Networks
175
Platform), a Decision Support System, Open Innovation module and, a Simulation Tool. As is stated before, Information and Communication Technologies (ICT) play an important role in distributed scenarios. In this context, ICT Platform should be a basis for the non-centralized decision making and has to integrate a simulation and optimization decision support software to evaluate alternative product-processessupply network resilient configuration for several customized demand scenarios and global manufacturing network conditions. Every future supply network member is interconnected through an ICT platform for an efficient real time collaborative planning/scheduling execution. The ICT platform (Fig. 5) incorporates interoperability functionalities, to facilitate the supply network member’s systems integration, and allow each new member a fast connection to the network. Service-Oriented Platform for Extended Business Process Management (SOP4EBPM) will support collaboration activities between REMPLANET Scenario members. Service-Oriented Architecture (SOA) [13] is a concept of Software Architecture that defines the utilization of services as basic constructions for application development. This architecture allows enterprises to improve its flexibility by decoupling business process logic from IT implementations. The ICT platform incorporates interoperability functionalities, to facilitate the supply network member’s systems integration, and allow each new member a fast connection to the network.
Fig. 4. ICT Platform View
A simulation and optimization decision support software will be used to evaluate alternative product-processes-supply network resilient configurations for several customised demand scenarios and global manufacturing network conditions. Relevant Key Performance Indicators (KPIs) like delivery time, cost, agility and flexibility metrics will be calculated as support to the final decision of the future network configuration responsible for placing the new product-service on the market.
176
D. Franco, G. Prats, R. de Juan-Marín
ICT Platform will allow partners to achieve strategies like mass customization, a concept that customers are demanding more every day. Open Innovation Platform will support members to achieve open innovation. It has been shown that both the efficiency and the effectiveness of innovation can be increased dramatically when innovation is not seen as a closed process conducted with one form, but as an open activity within a network of loosely-coupled actors, including the users of the product or service. This platform is supposed to enhance the implementation and continuous improvement of a mass customization system utilizing inputs for these processes from a wide non-hierarchical network of external partners. Finally, Fig. 6 shows the global view of the proposed ontology. Concepts are logically related in order to facilitate communication between project partners.
Fig. 5. Global Ontology View
As showed, REMPLANET Scenario can be formed by a company network, a group network in case the company is a member of a group, and by an external networks. This networks, are integrated of different classes of enterprises, of different sectors (manufacturing, logistics…) but all of them have in common that are connected to the ICT Platform that REMPLANET Scenario provides in order to achieve flexibility and preparedness to environments changes. Customer will be also connected to the ICT Platform, through its Open Innovation Platform due to the importance of integrating customers in the innovation process. This module also supports the concept of mass customization. Enterprises need
An Ontology Proposal for Resilient Multi-plant Networks
177
specific competencies in order to succeed mass customization. Open Innovation supported also by the Open Innovation Platform, will enable companies to co-create and learn in a horizontal network of other companies facing the same task. 4.1. Glossary Next, important concepts take into account in this paper, are defined: EBPM: an extended business process management model supports business activity integration across enterprises irrespective of the technical implementation of the business activity, the electronic data standards and the partner contracts used. Open Innovation: system where innovation is not solely performed internally within a firm, but in a cooperative mode with other external actors. Open innovation is characterized by cooperation for innovation within wide horizontal and vertical networks of customers, start-ups, suppliers, and competitors. Decision Support Systems: constitute a class of computer-based information systems including knowledge-based systems that support decision-making activities. Mass Customization: producing goods and services to meet individual customer's needs with near mass production efficiency. Open Innovation Platform: empowers innovation and increases its effectiveness throughout the supply chain. Service Oriented Platform: the SOP concept offers an application platform as a network service (inside or outside an enterprise firewall), providing a centralized runtime to execute and manage distributed or centralized applications. Business Opportunity: It is a time or occasion with favorable combination of circumstances that is suitable to start a business. Market Opportunity: newly identified need, want, or demand trend that a firm can exploit because it is not being addressed by the competitors. Company Network: provides an inter-firm relationship among suppliers and users which gives them the advantages associated with size while remaining small. External Network: is defined as the group of companies without current links with the company. Group Network: is defined as the group of companies to which the specific company belongs.
5. Conclusions In this paper we have introduced an ontology proposal for understanding concept interrelations of the REMPLANET scope. As we pointed out, it is a useful approach to capture and model in a comprehensive way the concepts that will appear in the project domain. It also allows the knowledge to be reused, shared, and enriched with more knowledge using templates and automated procedures. At this level of development, three main ontological concepts can be identified: Resilient Organization, ITC Platform and Members and its related processes. Despite this initial contribution, we still believe that some concepts should be further discussed, for example, the concept customer can be understood as an
178
D. Franco, G. Prats, R. de Juan-Marín
external customer, but, can be a member an internal customer? In the same way, can be an order an internal order, or it only can be an external order? Next, REMPLANET members will need to discuss this ontology proposal. It will be transferred to each member and the ontology will be detailed with additional concepts which are relevant to the project development. Finally, mention that the ontology was encoded in OWL, using the Protégé framework.
6. Acknowledgements The research leading to these results has received funding from the European Community's Seventh Framework Programme (FP7/2007-2013) under grant agreement n° NMP2-SL-2009-22933
7. References [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]
H. Chesbrough, The New Imperative for Creating and Profiting from Technology, Harvard Business School Press, 2003. IDEAS, “Interoperability Developments for Enterprise Application and Software roadmaps,” http://www.ideas-roadmap.net. 2005. INTEROP - DI.1b, “Deliverable DI.1b: Interoperability Knowledge corpus,” IST-1508011: Interoperability Research for Networked Enterprises Applications and Software (INTEROP), 2006. R. Poler, J.V. Tomás and P. Velardi, “Interoperability Glossary,” Deliverable 10.1, Interop Network of Excellence., 2005. Y. Naudet, T. Latour, K. Hausmann, S. Abels, A. Hahn and P. Johannnesonn, “Describing Interoperability: the OoI Ontology,” In Workshop on Enterprise Modelling and Ontologies for Interoperability (EMOI-INTEROP), 2006. D. Chen and F. Vernadat, “Enterprise Interoperability: A Standardisation View Interand-Intra Organizational Integration,” K. Kosante et al., Kluwer Academic Publishers, 2002, pages. 273-282. D. Chen and F. Vernadat, “Standards on enterprise integration and engineering - A state of the art.,” International Journal of Computer Integrated Manufacturing (IJCIM), vol. 17(3), 2004, pages. 235-253. D. Chen and N. Daclin, “Framework for Enterprise Interoperability,” IFAC EI2N Bordeaux, 2006. D. Chen, “Enterprise Interoperability Framework,” INTEROP Network of Excellence, 2006. T.R. Gruber, “A Translation Approach to Portable Ontology Specifications,” Knowledge Acquisition, vol. 5, 1993, pages. 199 – 220. M. Gruninger and M.S. Fox, “Methodology for the design and evaluation of ontologies,” In Proceedings of the Workshop on Basic Ontological Issues in Knowledge Sharing, IJCAI-95, 1995. M. Uschold and M. Gruninger, “Ontologies: Principles, methods and applications,” To appear in Knowledge Engineering Review, vol. 11, 1996. N. Bieberstein, S. Bose, M. Fiammante, K. Jones, y R. Shah, Service-Oriented Architecture (SOA) Compass, IBM Press, 2006.
Collaboration Knowledge Ontologies to Support Knowledge Management and Sharing in Virtual Organisations Muqi Wulan1, Xiaojun Dai2, Keith Popplewell1 1
Faculty of Engineering and Computing, Coventry University, Coventry, CV1 5FB, UK Department of Mechanical Engineering, University of Birmingham Birmingham B15 2TT, UK
2
Abstract. This paper focuses on representing collaboration knowledge in the context of a Virtual Organisation (VO). Knowledge representation embodies the characteristics of a VO from its incubation, formation, operation and termination. It is necessary to scope and identify all the collaboration knowledge utilised in a VO’s life cycle. The classification of collaboration knowledge or knowledge repositories is described in terms of 3 different types of organisations: individual enterprises, collaboration pools and VOs. Therefore collaboration knowledge falls into three main categories: enterprise knowledge, collaboration pool knowledge and VO knowledge. Later they are elucidated in ontology. The terms and concepts are defined and considered to be consistent with each other. Keywords: knowledge management, knowledge sharing, ontology, collaboration, VO
1. Introduction Virtual Organisations (VOs) emerge as a response to fast-changing markets. A VO is a temporary business alliance of independent enterprises based on network technology [1]. These enterprises collaborate together to complement each other’s core competences and resources in order to generate new solutions on a common business objective which may not be achieved by a single enterprise. Being virtual provides a vision appropriate for not only large businesses but also small and medium enterprises (SMEs). As we know knowledge management has already been one of the most indispensable strategies for an organisation or an enterprise to maintain its competitive advantages and core competences over its rivals [2]. Being a new organisational form, VOs should have similar requirements and face even more complicated issues on knowledge management. Compared to that in a single
180
M. Wulan, X. Dai, K. Popplewell
enterprise, knowledge management within a VO is involved in more perspectives and more levels since there are several different forms and sizes of organisations acting and interacting in the process of a VO’s life cycle. At the same time being virtual brings new challenges on how to effectively manage virtual resources along with physical and human capital [3].. On the other hand knowledge management in a VO is typified by the need to both share and protect knowledge. Sharing of knowledge between enterprise partners is critical to the success of any network organisation whilst commercially valuable expertise and IPR possessed by the individual enterprise should be protected in a secure way. From the individual enterprise’s point of view, it may share knowledge either within the enterprise or with external collaborating enterprises [4]. It is understandable that there are notable differences in approaches to internal and external knowledge sharing. This paper addresses the requirements for an ontology of VO and related knowledge: (1). Firstly, at the macro level it is essential to identify the categories of organisations that occur in VO collaboration, and how these organisations behave in the process of forming, operating and terminating the VO. (2). Through analysis of each organisation category’s characteristics, the knowledge which needs to be utilised and managed in a VO can be linked to the category of organisation. In this context the knowledge is called collaboration knowledge. In order to share collaboration knowledge in the activities of virtual collaboration, it is structured and represented in an ontology. (3). A related paper [5] will address the issues of service architecture to support knowledge management and sharing in the VO.
2. Evolution of Collaboration We summarise a VO’s life cycle into four stages: pre-creation, creation, operation and termination. Since a VO is founded by individual enterprises to address a specific business opportunity (BO), initially there must be a number of candidate enterprises joining together to explore potential collaboration. This is the stage of pre-creation where the infrastructure is set up for enterprises to register, publish their capabilities, look for possible collaborative partners and find BOs. Having identified a BO worth further development, in the second stage (creation), the enterprise partners start to investigate and assess the possibility of establishing a VO from financial and technical perspectives. As a result a legal agreement for the VO may be reached with a clear definition of collaboration objectives and business partners. Now a VO is brought into being and its life cycle enters the stage of operation. During this phase the identified partners contribute to the actual execution of the VO tasks by executing pre-defined business processes. This phase is also featured by monitoring of the performance and the enforcement of policies in the VO. When the objectives of the VO have been fulfilled it must be dissolved, closing the infrastructure, archiving VO related documents and information, evaluating the collaboration for evolution of new knowledge and rate all
Collaboration Knowledge Ontologies to Support KM and Sharing in VOs
181
participating enterprises. These key activities are carried out in the last phase of VO’s lifecycle - VO’s termination. As to the categories of organisations in a VO, the VO itself is clearly one category. It is also not difficult to identify that the individual enterprises constitute another distinct category: they are physically entities having their own capabilities and core competences relevant to a collaboration. Although highly developed IT infrastructures provide the possibility of VO’s realisation, the “traditional” issues of trust, security and profit sharing among partners still remain at the heart of collaboration. Trust is determined to be the main inhibiting factor for creating collaborative environment like the VO. Trust building between partners is an essential requirement for development and smooth working of a VO [6]. The VO breeding environment (VBE) was proposed to foster successful generation of VOs, especially for long-term collaboration [7]. Hence in the early phases of a VO’s life cycle, we can identify a third category of organisation working for creating a VO. In the context of this research we name it a Collaboration Pool (CPool) where the activities, culture and policies of different organisations can be identified and which helps these organisations build up common understanding. The concept of a collaboration pool certainly includes VBE, but also embraces a wider range of possibly less formal associations, with or without formal brokers or managers. Compared to VOs and individual enterprises, a collaboration pool is loosely coupled.
3. Collaboration Knowledge and Knowledge Repositories Collaboration knowledge relating to a VO is also structured by these organisational categories, and can be structured and implemented in a knowledge repository. The knowledge repository, or organisational memory, is an ICT system that systematically captures, organizes and analyses the knowledge assets of an organization. This is a collaborative system where people can search, browse, retrieve and preserve organizational knowledge in order to facilitate collaborative working inside an enterprise or with enterprise partners. Frequently the structure of one organisation bears almost no resemblance with the others’ in vision, activity, human resource, management strategy and communication methods. Because we have identified three different categories of organisations - individual enterprises, VOs, and CPools, collaboration knowledge in a VO respectively consists of three main parts: enterprise knowledge (EK), collaboration pool knowledge (CPK) and VO knowledge (VOK). The collaboration knowledge in each category of organisation is collected and extracted by analysing business behaviours activities, and modelled into each organisation’s knowledge repository. Ontology has been widely accepted as a formal and explicit representation of shared conceptualisation, which can be used and reused in order to facilitate comprehension of concepts and relationships in a given domain, and communication between different domain actors by making the domain assumptions explicit [8]. For a VO, collaboration partners might come from different fields or follow a different philosophy, it is necessary to introduce a mechanism to share common understanding on knowledge and to agree on a
182
M. Wulan, X. Dai, K. Popplewell
controlled vocabulary used to communicate. In the following subsections three categories of collaboration knowledge will be described. 3.1. Approach Adopted in Knowledge Representation In developing an ontology of collaboration knowledge on which to base web services for knowledge management and sharing in collaboration [5], the ontology language OWL DL (RDF S) [9] and the standard OWL 1.0 [10] are used to represent the ontologies in three main categories: Enterprise Knowledge (EK), Collaboration Pool Knowledge (CPK) and Virtual Organisation Knowledge (VOK). This assures consistency in terminology. The ontology development software/tool Protégé and plugin Graphviz are used to define and develop the knowledge ontology. There is a four-phase approach to be employed: preparatory phase, anchoring phase, iterative improvement and application phase. 3.2. Enterprise Knowledge Ontology Through describing shared concepts and relationships within an enterprise, the enterprise ontology (EO) provides an overview of an enterprise, characterise resources/knowledge possessed and how resources/knowledge are used. Recently developed EOs, such as AIAI [11] and TOVE [12], focus on generic models and enterprises’ general business activity independent of a particular application domain or sector. However, from examination of the above enterprise ontology proposals, it is difficult to define a common ontology for enterprises which can accommodate the terminology of different industry sectors. In the EO developed here, the top level is generic and applicable to more than one domain. The detail level deals with domain specific terminology, for example, for the manufacturing sector. This EO is adapted from Factory Data Model (FDM) [13] which defined the terms and their relationship within the manufacturing sector. The top-level ontology of this EO for manufacturing domain is depicted in Fig. 1 where six basic classes are defined. Resource includes human resource, manufacturing machinery and tooling etc., computing facilities etc. needed to carry out a process. Strategy includes all the knowledge and methods used to make decisions throughout the enterprise. Process includes both manufacturing and business processes. Facility includes organisational units such as factory, shop, cell, as well as administrative, commercial and decisional units. Flow objects connect independent processes into a system with a purpose. Token represents business objects (products, information and documents etc.) created and used by processes and transferred through flows.
Collaboration Knowledge Ontologies to Support KM and Sharing in VOs
183
Fig. 1. Top level of an Enterprise Ontology
The Facility can be an enterprise having Strategy, Resource and Process to plan and implement its business objective. The Enterprise’s Strategy controls Process and allocates Resource. Token represents the enterprise’s business object which is subject to the Flow class to link the Process. 3.3. Collaboration Pool Knowledge Ontology A collaboration pool (CPool) consists of potential collaboration partners which are enterprises willing to cooperate with each other and exploit a promising business opportunity. Inside a CPool, the members will exchange certain amount of knowledge and information, which may be a part of the enterprise’s own knowledge together with CP Knowledge, relevant only to the CP as a whole, rather than individual members. The purpose of a CPool is to let each member’s core competences be known within the CPool and help building up better trust among members. In order to maintain common understanding of CP Knowledge we define a CP ontology. The basic classes and their relationships in the CP ontology are illustrated in Fig. 2. A CollaborationPool consists of CPMmembers who intend to identify a BusinessOpportunity. The CollaborationhPool has CPAsset for managing and running CollaborationPool. Each CPMember has a CPMemberProfile and has a CPRole at least to be included in CPTask. A CollaborationPool aims to breed a VirtualOrganisation in response to certain BusinessOpportunity. A VirtualOrganisation has VOPartners. Both CPMember and VOPartner can be Enterprises.
184
M. Wulan, X. Dai, K. Popplewell
Fig. 2. Basic classes and relationships in a Collaboration Pool Ontology
3.4. VO Knowledge Ontology
Fig. 3. Basic classes and their relations in a VO Ontology
A VO is formed when members of a CP have identified a BO and respond to it. A VO is a short-term association with a specific goal of acquiring and fulfilling a BO [8]. However, despite the short term nature of the VO, to operate successfully business partners in a VO must share knowledge and information to a significant degree. Knowledge about each individual partner is enterprise knowledge. This may be available to other partners in the VO, subject to access control restrictions protecting confidentiality and critical IPR. In addition there is a body of knowledge
Collaboration Knowledge Ontologies to Support KM and Sharing in VOs 185
which is relevant to the VO as a whole, regarding structural and operation aspects of the VO. The VO ontology therefore describes the terminology in VO Knowledge. The basic classes and their relations of a VO are presented in Fig. 3.
4. Conclusions The paper discussed the issues of knowledge management for VOs from the perspective of knowledge ontologies for the evolving categories of organisation which are involved in VO collaboration. In the analysis of a VO’s life cycle three different types of organisations are identified to work within the context of a VO. They are individual enterprises, collaboration pools and virtual organisations. Thus collaboration knowledge contributing to a VO can be classified into three categories and represented in an ontology. This ontology can in turn be used to structure a knowledge repository which is comprised of knowledge bases for individual enterprises (EKB), collaboration pools (CPKB) and virtual organisations (VOKB). This forms the foundation for development of a software service architecture which supports population, application and evolution of knowledge in these knowledge bases, reflecting the developing experience of partners in collaboration, which is reported in a related paper [5].
5. Acknowledgements This work is fully supported by the European Union funded 7th framework research project – Supporting Highly Adaptive Network Enterprise Collaboration Through Semantically-Enabled Knowledge Services (SYNERGY).
6. References [1] [2] [3] [4] [5]
[6]
Luczak H, Hauser A, (2005) Knowledge management in virtual organizations, Proceedings of International Conference on Services Systems and Services Management. vol. 2, 898 – 902 Geisler E, Wickramasinghe N, (2009) Principles of knowledge management: theory, practices and cases, M.E. Sharpe Klobas J, Jackson P, (2008) Being virtual: knowledge management and transformation of the distributed organisation, Physica-Verlag Kess P, Phusavat K, Torkko M, Takala J, (2008) External knowledge: sharing and transfer for outsourcing relationshops, International Journal of Business and Systems Research, vol.2, no.2, 196-213 Wulan M, Dai X, Popplewell K, (2010) Collaboration knowledge management and sharing services to support a Virtual Organisation, accepted by the International Conference on Interoperability for Enterprise Software and Applications, Coventry, UK Ellman S, Eschenbaecher J, (2005) Collaborative network models: Overview and functional requirements, Virtual Enterprise Integration: Technological and organizational perspective, eds. G.Putnik, M.M. Cunha, Idea Group Inc., 102-103
186
M. Wulan, X. Dai, K. Popplewell
[7]
Camarinha-Matos L, (ed), (2004) Virtual Enterprise and Collaborative Networks, Kluwer Academic Publishers, USA Plisson J, Ljubic P, Mozetic I & Lavrac N, (2007) An ontology for virtual organisation breeding environments, IEEE Transactions on Systems, Man, and Cybernetics – Part C: Applications and Reviews, vol. 37, no. 6, 1327-1341 W3C, (2004 a) OWL/RDFS: Section 1.4 of OWL Web Ontology Language Guide, available at http://www.w3.org/TR/2004/REC-owl-guide-20040210/ W3C, (2004 b) OWL 1.0 Standard: OWL Web Ontology Language Guide, available at http://www.w3.org/TR/2004/REC-owl-guide-20040210/ Uschold M, King M, Moralee S & Zorgios Y, (1998) The Enterprise Ontology, The Knowledge Engineering Review, vol.13, no.1, 31-89 Fox MS, (1992) The TOVE Project: A Common-sense Model of the Enterprise, Industrial and Engineering Applications of Artificial Intelligence and Expert Systems, Belli, F. and Radermacher, F.J. (Eds.), Lecture Notes in Artificial Intelligence # 604, Berlin: Springer-Verlag, 25-34 Harding J, Yu B, Popplewell K, (1999) Organisation and functional views of a small manufacturing enterprise, International Journal of Business Performance Management, vol.1, no.3, 338-352
[8] [9] [10] [11] [12]
[13]
Mediation Information System Engineering for Interoperability Support in Crisis Management Sébastien Truptil1, Frédérick Bénaben1, Nicolas Salatgé2, Chihab Hanachi3, Vincent Chapurlat4, Jean-Paul Pignon5 and Hervé Pingaud1 1 2 3 4 5
Centre de Génie Industriel – Université de Toulouse, Mines Albi – Campus Jarlard, Route de Teillet, 81013 ALBI Cedex 09 (FR) PEtALS Link (formerly EBM WebSourcing) – 4, Rue Amélie, 31000 TOULOUSE (FR) Institut de Recherche en Informatique de Toulouse – Université de Toulouse 1 – 2, Rue Doyen Gabriel Marty, 31042 TOULOUSE Cedex (FR) Laboratoire de Génie Informatique et d’Ingénierie de Production – Ecole des Mines d’Alès – Parc scientifique Georges Besse, 30035 NIMES Cedex 1 (FR) THALES Communications – 160, Boulevard de Valmy, BP82, 92705 COLOMBES cedex (FR)
Abstract. One objective of the French-funded (ANR-2006-SECU-006) ISyCri Project (ISyCri stands for Interoperability of Systems in Crisis situation) is to provide the crisis cell in charge of the situation management with an Information System (IS) able to support the interoperability of partners involved in this collaborative situation. Such a system is called Mediation Information System (MIS). This system must be in charge of (i) information exchange, (ii) services sharing and (iii) behavior orchestration. This article proposes, first, an approach of MIS engineering in crisis context. This design method is model-driven and uses model morphisms principles and techniques. Furthermore, due to the intrinsically evolutionary nature of crisis phenomenon, the MIS must remain adapted to the situation and to the panel of partners involved. This paper presents also the MIS on the fly adaptation, based also on model-driven approach in order to provide agility to the MIS. Keywords: Information System, Interoperability, Mediation, Ontology, Crisis, Modeldriven engineering
1. Introduction As for the ISyCri project, a crisis is an abnormal situation [1], which occurs suddenly and impacts an ecosystem with unacceptable consequences. Such a break into the continuous state of the considered (eco)system implies to deal with the crisis management through a dedicated cell of actors in charge of the crisis
188
S. Truptil, F. Bénaben, N. Salatgé, C. Hanachi, V. Chapurlat, J.P. Pignon H. Pingaud
response. First, there are actors on the field, using their specific abilities in order to perform business activities (such as evacuating injured persons, fixing a road, etc.). Second, there are heads of these actors on the field, grouped into a crisis cell (and potentially directed by a single authority). The ISyCri project [2] focuses on this crisis cell and on the question of the coordination of the partners inside the crisis cell. This objective may be separated in two questions. The first point is the following: according that partners of the crisis reduction have the competences and the business procedures to act as suitable as possible on the field of the crisis, how is it possible to help to manage, to coordinate and to synchronize this set of operational experts from the crisis cell? The second part of this article aims at presenting the proposed conceptual solution based on mediation considerations (especially between Information Systems). The third part of this article presents more specifically the developed approach, which aims to (help to) define, at the beginning of the crisis, (i) the appropriate collaborative behavior through a collaborative process model and (ii) the dedicated Mediation Information System (MIS) able to support the previously identified collaborative process with a service-oriented technology. The second point is the following: considering crisis management, there are three main instability factors: • a crisis situation is, by nature, potentially unstable (the system is damaged and replicas or over-crisis may occurs at any time); • the crisis cell itself may be a very weak collaborative network, which might be unstable too (sporadic collaboration, partners unused to work altogether, often from heterogeneous business fields or culture); • the knowledge concerning the situation is certainly incomplete and constantly evolving, providing instability into the management system. The question is so: How to ensure that the solution proposed for the first question (the MIS) remains adapted to the evolving crisis situation? The fourth part of this article explains the conceptual and technical solutions proposed to support this agility requirement of the MIS. Finally, the fifth section of this article concludes and presents some perspectives for this work.
2. Management of Heterogeneous Actors of the Crisis Cell 2.1. The Main Question and its Refinements When a crisis occurs, several actors are involved simultaneously to solve (or at least to reduce) the situation. The question is then: “How to provide this set of heterogeneous actors with the ability to organize and coordinate their actions in an optimal manner”. Depending from the type, the size and the location of the crisis, this organization may be more or less formalized. The first hypothesis of this work is that this collaborative organization is based on a crisis management cell, which may be seen as a decision center. The question is then changed into: “how
Mediation Information System Engineering
189
to provide the crisis cell with the ability to organize and coordinate the actions of partners in an optimal manner”. Interoperability is defined in [3] by the European network of excellence InterOp as “the ability of a system or a product to work with other systems or products without special effort from the customer or user”. It is also defined in [4] as “the ability of systems, natively independent, to interact in order to build harmonious and intentional collaborative behaviors without modifying deeply their individual structure or behavior”. Considering these definitions we propose to consider that the question is, at this point, the following “how to support the interoperability of actors into the crisis cell”. We believe that the crisis cell can be seen as a system of systems (SoS). According to [5], there are five criteria to define a SoS: 1. 2. 3. 4. 5.
Operational independence of the elements (systems) Managerial independence of the elements (systems) Evolutionary development of the system of systems Emergent behavior of the system of systems Geographical distribution of elements
The crisis cell concerns elements (actors), which are, by definition, independent on the operational and managerial plans. They are ISs from different organizations with different competencies (on the operational level) and different heads (on the managerial level). The crisis cell is, furthermore, an evolving entity. New actors may join the cell while some other may quite it. Moreover, the behavior of the crisis cell is adapted to the crisis to solve and is following the evolutions of the situation. Finally, even if actors may be in the same room, first, the crisis cell may be distributed in several places and, second, members of the crisis management cell “exchange only information and not substantial quantity of mass or energy” (which is the sub-definition of the fifth criterion). The crisis cell can be considered as a system of systems and the question is so the following: “how to support the interoperability among the SoS of the crisis cell”. 2.2. Ideas and Tracks to Answer the Main Question An important point is that the members of the crisis cell are, on the one hand, communicating with their operational resources on the crisis field through their own channels. Another assumption of this article is that members of the crisis cell are able to use these specific means of communication to receive incoming reports and to send outgoing instructions. However, the central issue is that the members of the crisis cell are, on the other hand, not used to exchange information between each other. If they expect to organize and coordinate their actions, they need to find a way to support their exchange of information into the crisis cell. Information systems are so at the center of the topic of this article and the system of systems of the crisis cell will be considered through the information system point of view. Considering [6], we believe that interoperability of ISs into the crisis cell may not be assumed through a peer-to-peer architecture. Such a solution would imply too much interfaces to ensure the efficiency of collaboration (each partner’s IS would need to be able to interact capably with too much other ISs with an
190
S. Truptil, F. Bénaben, N. Salatgé, C. Hanachi, V. Chapurlat, J.P. Pignon H. Pingaud
unavoidable exploding numbers of potential connections). Furthermore, as we stated in the previous section that the crisis cell may be seen as a SoS, contributing systems will be considered as “functions provider” for the crisis cell (functions that they would be able to ensure on the operational field by activating their operational resources thanks to their own channels) and will be seen as split in two parts: public part (involve in the collaborative network of the crisis cell) and private part (dedicated to its own behavior, according to SoS considerations). This characteristics matches with the framework proposed in [6] and the proposed conceptual solution is so a Mediation Information System (MIS) dedicated to support interoperability of ISs of the SoS of the crisis cell. 2.3. Architecture of the MIS We propose to consider the MIS according to a three layers model: 1.
2.
3.
Business layer: presents the exchange of information, the management of services (which use and deal with information) and the orchestration of the collaborative process (which use and deal with services and information). The definition of this layer is strongly motivated by the mediation conclusion of previous section. Logical layer: presents the service-oriented architecture (SOA), which is strongly motivated by the business layer. This layer includes three different views perfectly coherent with the previous layer (information view, service view and process view). PIM4SOA results and SoaML inspire this layer [7]. Technical layer: concerns the choice of an enterprise service bus (ESB), which is one of the best platform to deploy a SOA solution and is so strongly motivated by the logical layer. Such a technical solution provides a middleware and a workflow engine to coordinate services.
One important remark is that another assumption of this article concerns the fact that partners of the crisis cell use SOA principles.
3. MIS Engineering in a Crisis Context: Theory and Example The three levels model presented in the previous section corresponds exactly to the model-driven architecture defined by OMG [8]. The business level matches with the CIM layer (Computer Independent Model), the logical level corresponds with the PIM layer (Platform Independent Model), while the technical level fits with the PSM layer (Platform Specific Model). 3.1. Model Transformation in a Model-driven Approach Considering this model-driven issue, the crucial point of the presented approach is model transformation, which may be synthesized as follow :
Mediation Information System Engineering
191
Fig. 1. Model transformation principle
A source model is used (built according to a source meta-model (MM)). The key point is that the source MM shares part of its concepts with the target MM (the two spaces, source and target, have to be partially overlapping in order to allow modelmorphism). As a consequence, the source model embeds a shared part and specific part. The shared part provides the extracted knowledge, which may be used for the model transformation, while the specific part should be saved as capitalized knowledge in order not to be lost. Then, mapping rules (built according to the overlapping conceptual area of MMs) can be applied onto the extracted knowledge in order to provide the transformed knowledge. That transformed knowledge and an additional knowledge (to fill le lack of knowledge concerning the non-shared part of concepts into the target MM) may be finally used to create the shared part and the specific part of the target model. 3.2. Example of MIS Engineering in Crisis Context February the 27th, 10 AM, the police is informed that an accident between a tanktruck and a train. Both of them contain unknown materials, potentially dangerous, which are currently escaping in the atmosphere. Policemen sent in the area and railway-station employees are unconscious while children of the nearest school are feeling sick. This is an overview of the scenario used to run the whole approach of MIS engineering (originally this is a CBRN exercice). The following presents the different steps of the design and the associated concrete results. First of all, based on a crisis situation meta-model presented in [2], a modeling tool has been designed (thanks to GMF environment [9]). This modeling tool allows the user to characterize the situation in terms of (i) people, goods and natural sites impacted, (ii) characteristics of the crisis (trigger-event, known facts, existing risks, potential danger, aggravating factors) and (iii) available resources and rescuers. The following picture presents the obtained model.
192
S. Truptil, F. Bénaben, N. Salatgé, C. Hanachi, V. Chapurlat, J.P. Pignon H. Pingaud
Fig. 2. CBRN characterization model
Another tool, presented in [10], is dedicated to describe services of partners in order to define (before or at the beginning of the crisis) what are the functions available for each partner and what are the technical specificities of these services. The second step of the engineering process is to use an ontology framework to extract all the damaging facts and all the risks of the situation in order to rank them, according to the user point of view (the tool assists the user but the head of the crisis cell has to decide which risk or impact should be treated first). In our example, we propose to sort these elements as follows (they are the main identified facts/risks, others exist but, for the moment, they are not considered as priorities): (1) Prevent risk of explosion, (2) Prevent risk of contamination, (3) Care sick people, (4) Prevent risk of panic. Then according to the defined services, a first version of the collaborative process is deduced (in BPMN [11]) in the third step, and proposed to the crisis cell, which can modify, improve or validate this model. Furthermore, another tool, not described here but fully presented in [12], is used at this level to check and validate the proposed model through an anticipative effect-based approach. This step improves the robustness of the deduced collaborative process model and enriches the approach with a verification/validation stage. The obtained result of the deducing and improving phases is presented on the following figure:
Mediation Information System Engineering
193
Fig. 3. Collaborative process model (BPMN) of the CBRN example – CIM level
Regarding section 1.3.1, this CIM model has been obtained thanks to a model transformation mechanism: The source meta-model is the crisis situation metamodel used in the characterization tool, the target meta-model is the collaborative process meta-model described in [13] while the additional knowledge is the order of critical risks and facts. The mapping rules are described in [2]. The fourth step concerns the PIM level and proposes to obtain the logical architecture of the MIS, according to the previous collaborative process model. This model transformation provides an UML diagram. The following UML diagram is an extract corresponding to the service of actor setSecurityPerimeter :
Fig. 4. Extract from the SOA MIS model (UML) of the CBRN example – PIM level
Regarding section 1.3.1, this PIM model has been obtained thanks to a model transformation mechanism: The source meta-model is the previously used collaborative process meta-model, the target meta-model is the SOA meta-model described in [14] while the additional knowledge is the added profile for services. The mapping rules are also described in [14].
194
S. Truptil, F. Bénaben, N. Salatgé, C. Hanachi, V. Chapurlat, J.P. Pignon H. Pingaud
The fifth step concerns the PSM level and proposes to obtain the technical structure of the MIS, according to the previous logical architecture model. This model transformation provides an UML diagram. The following UML diagram is an extract corresponding to the service of actor setSecurityPerimeter :
Fig. 5. Extract from MIS technical model (UML) of the CBRN example – PSM level
Regarding section 1.3.1, this PSM model has been obtained thanks to a model transformation mechanism: The source meta-model is the previously used logical SOA architecture meta-model, the target meta-model is the ESB meta-model described in [15] while the additional knowledge is the added profile for services. The mapping rules are also described in [15]. Finally, the deployment of the MIS on the ESB PEtALS [16] is presented on the following figure: Fight Explosion
Set Security Perimeter
How Many People To Rescue
Set Equipment
Rescue People
Maintain Perimeter
Set Medical Post
BringPeople To MedicalPost
Care People
Fig. 6. ESB deployment (PEtALS) on the CBRN example – PSM level
4.MIS Agility in a Crisis Context Due to the obvious instability of crisis situation, agility, as the ability to adapt to change, is a crucial requirement for a crisis cell, and for its mediation information system. According to [17], [18] and [19], agility may be seen as “an ability to
Mediation Information System Engineering
195
satisfy a change in a short time”. In the context of ISyCri project, the notion of agility is considered as the combination of reactivity (as an ability of short time reaction) and flexibility (as an ability of following the needs). The main factor of MIS agility is based on the MIS engineering approach and especially the MIS reengineering approach. Indeed, this design method has been implemented into an ESB where each tools of each step has been plugged has a service. Then, the native plasticity of the workflow orchestration of that platform may be used in order to reconfigure the MIS. The following picture presents the overview of the “design-ESB” with the tools presented in section 1.3.2 as services: Crisis Modeling Tool
Service Modeling Tool
Collaborative Process Modification Tool
Rank Risk, Consequence Tool
PIM Model Transformation
Collaborative Process Deduction
PSM Model Transformation
Collaborative Process Validation Tool
Deployment of MIS
Fig. 7. ESB (PEtALS) dedicated to support the engineering/reengineering of MIS
According to this figure and depending from the need of change, three levels of agility are available: 1. 2.
3.
If the crisis evolves in a consequent manner (the characterization model is no longer acceptable at all), the obvious solution is to restart the whole process. This is the large loop. If the crisis does not evolve but the collaborative network change (one actor leave, one other join the group, etc.), then the crisis characterization remain acceptable but the services available to manage the situation are no longer the same. The process should redefine the services and restart the deduction chain (with the same crisis model). This is the medium loop. If the process needs to be improved on the fly, then, interruption during the orchestration may allow the crisis cell to use late binding to choose the most appropriate service at the right moment, as explained in [20]. This is the small loop.
5. Conclusion and Perspectives The presented works aims at providing a crisis management cell with a set of structured tools, based on model-driven principles, to build a mediation information system able to support the interoperability between ISs in a crisis context. These tools run model transformations to dive into abstraction layers by
196
S. Truptil, F. Bénaben, N. Salatgé, C. Hanachi, V. Chapurlat, J.P. Pignon H. Pingaud
fulfilling business level, logical level and technological level. Assumptions are the following: (i) the crisis management is assumed by a crisis cell, (ii) each partner of the crisis cell is able to ensure the communication with its own resources on the operational field and finally, (iii) each partner of the crisis cell is able to propose a set of services corresponding to the reflect of its concrete operational abilities. The two first ones could not be changed for the moment, but concerning the third one an interesting perspective may be the support of service design. This track concerns the assisted conception of technical services, according to interfaces patterns and business services analysis. One obvious limit of this work is that, for the moment, there is no data translation in the workflow. All the partners have to use the same information models. The current work on mediation services embedded in the bus, and a starting PhD on semantic reconciliation, should be a nice track for this situation. Finally it is also possible to claim that a single collaborative process is maybe a too poor model to describe the business level. Another PhD is also starting to enrich the business and logical layers in order to provide a more complete knowledge for model transformation.
6. References [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]
Bénaben F, Pignon JP, Hanachi C, Lorré JP, Chapurlat V, (2007) Interopérabilité des systèmes en situation de crise. WISG’07. France. Truptil S, Bénaben F, Pingaud, H (2009), Collaborative process design for Mediation Information System Engineering. ISCRAM’09, Sweden. Konstantas D, Bourrières JP, Léonard M, Boudjlida N, (2005), Interoperability of Enterprise Software and Applications, IESA’05, Springer-Verlag, Switzerland.. Pingaud H, (2009), Prospective de recherches en interopérabilité : vers un art de la médiation ?. CIGI’09, France. Maier MW, (1998) achitecting principles for systems of systems, Systems Engineering, vol.1, n°4. Wiederhold G, (1992) Mediators in the Architecture of Future Information Systems, IEEE Computer magazine, Vol 25 N 3, 38-49. Benguria G, Larrucea X, Elveseater B, Neple T, Beardsmore A, Friess M,(2006) A Platform Independent Model for Service Oriented Architectures. IESA’06. OMG (2003), MDA guide version 1.0.1, document number : omg/2003-06-01 edition. Graphical Modeling Framework : www.eclipse.org/gmf. Truptil S, Bénaben F, Couget P, Lauras M, Chapurlat V, Pingaud H (2008) Interoperability of Information Systems in Crisis Management: Crisis Modeling and Metamodeling. IESA’08. Germany. BPMN : Business Process Modeling Notation. www.bpmn.org Daclin N, Chapurlat V, Bénaben F, (2009) A verification approach applied for analyzing collaborative processes: the Anticipative Effects-Driven Approach. INCOM’09. Moscow, Russia. Rajsiri V, Lorré JP, Bénaben F, Pingaud H, (2009) Knowledge-based system for collaborative process specification. Special issue of Computers in Industry, Elsevier. Touzi J, Bénaben F, Pingaud H, Lorré JP, (2008) A Model-Driven approach for Collaborative Service-Oriented Architecture design. Special issue of International Journal of Production Economics. Elsevier.
Mediation Information System Engineering
197
[15] Wenxin M, (2009) Model Transformation Research from Logical to Technical Model in MISE project. Master Report, France. [16] PEtALS : http://petals.objectweb.org [17] Kidd TP, (1994) Agile Manufacturing: Forging New Frontier. Addison-Wesley. [18] Lindberg P (1990) Strategic manufacturing management: a proactive approach, International Journal of Operation and Production Management, Vol 10, n°2. [19] Sharifi H, Zhang Z, (1999) A methodology for achieving agility in manufacturing organizations: An introduction. International Journal of Production Economics, 62. [20] Van der Aalst WMP, Basten, T (1999) Inheritance of Workflows: An approach to tackling problems related to change. Computing Science Reports 99/06.
Service Value Meta-model: An Engineering Viewpoint Zhongjie Wang1, Xiaofei Xu1, Chao Ma1, Alice Liu2 1 2
Research Centre of Intelligent Computing for Enterprises and Services (ICES), Harbin Institute of Technology, Harbin, China 150001 IBM China Research Laboratory, Beijing, China 100094
Abstract. Various tangible or intangible values are the ultimate outputs of service systems. In service engineering, the comprehensive description of service value is a key step that helps service engineers design and develop high-quality interoperable service systems that will deliver expected values to customers and providers. In this paper, a service value metamodel is put forward from an engineering point of view. First, the objective of service value modeling is extensively analyzed. Then, the various essential aspects of service value that have significance for service system design are presented and each aspect is illustrated in detail by a set of concepts. Based on this meta-model, a multi-level service value model and the corresponding value-oriented service engineering process are briefly introduced. Keywords: service engineering, service modeling, service value, meta-model, value-aware
1. Introduction Service modeling is a critical step in service engineering [1] and the quality of service models determines the quality of service systems to a great extent. Core components of a service model are the interactive co-production behaviors and processes between customers, enablers, and providers. In addition, people, resources, shared information, techniques, environment, etc, are essential constituents [2]. At present, there are massive service model specifications and modeling methods that are widely applied in practice, e.g., BPMN [3]. Besides the above-mentioned functional service elements, “value”, as the ultimate goal of a service, should occupy an important place in service models [4]. As service is defined as a co-production process to create and share value [2], various tangible and intangible values are regarded as the output of a service system. Quality of a service system depends on whether and to what degree it can provide expected values to customers and providers. From this viewpoint, “value” needs to be accurately characterized in service models and connected with functional elements, thereby helping service engineers evaluate and optimize models for future high-quality service systems.
200
Z.J. Wang, X.F. Xu, C. Ma and A. Liu
Researchers put forward various value models, e.g., the value network and e3Value, to describe value flow and exchange relationships. A value network is a complex set of social and technical resources which work together via relationships to create social goods (public goods) or economic value [5]. It is mainly used as a tool to plan, organize, control and harmonize the co-production process between organizations to help enterprises optimize the service process and achieve optimal business performance. e3-value model is an ontology-based methodology for “identifying and analyzing how value is created, exchanged and consumed within a multi-actor network, hence, taking the economic value perspective and visualizing what is exchanged and by whom” [6]. Although there have been such value-oriented models, they emphasize particularly the value exchange relationship from a financial point of view. From an engineering viewpoint on service system design, they are quite insufficient. To help service engineers explicitly describe values from all essential aspects, in this paper we present a service value meta-model which is composed of a set of basic concepts to facilitate value-aware service engineering and methodology (VASEM). It is worthwhile to note that, as a service system is a socio-technological system that is composed of “any number of elements, interconnections, attributes, and stakeholders interacting to satisfy the request of a known client and create value” [7], it is usually considered as an interconnected system (or called “system of systems”). When designing such a complex system, interoperability issues must be elaborately addressed to facilitate value co-production between systems of different service participants. Therefore it is necessary to reach a consensus on how to describe service values uniformly, which is of great significance on developing the system from an engineering viewpoint.
2. Objective of Service Value Modeling The objective of service value modeling is to describe values that are to be delivered by service systems and to connect values with functional elements, thus to help service designers analyze whether and to which degree these expected values are implemented in aid of the service models. To meet this objective, service value models should have the ability to answer the following questions: (1) For each customer and provider, what are his value expectations? (2) How are these values co-produced, transferred, transformed, decomposed, composed, and allocated among participants? (3) How are values measured? (4) How are values inter-dependent with each other? (5) What is the lifecycle of each value? (6) How and to what degrees are these values to be implemented under the support of functional service elements?
Service Value Meta-model: An Engineering Viewpoint
201
3. Service Value Meta-model 3.1. Top Level of the Meta-model Fig. 1. shows the top level of the meta-model. When a service system (ServiceSystem) is to be designed and developed to realize a specific service (Service), designers need to create not only functional models (FunctionModel) but also value models (ValueModel). Functional models focus more on describing how a service is actualized by a set of functional elements (FunctionalElement) and relations between them (ElementRelation). Value models (ValueModel) emphasize the service’s tangible/intangible output expected by customers and providers. Service
<>
ServiceSystem
ValueModel
FunctionModel
1
1 1..n
ServiceValue
ValueRelation 1..n
1..n
ValueMapping
ElementRelation
FunctionalElement
1
1
1..n
+ValueType 1
ValueTaxomony
1
ValueLifecycle
1
DeliveryMeans
1
ValueIndicatorSet
Fig. 1. Top level of service value meta-model
A ValueModel is composed of a set of values (ServiceValue) and the relationships between them (ValueRelation). Each ValueRelation connects one value with one or multiple other values. When a service is designed, which values are to be coproduced and delivered are first identified and relations between them are clarified. Afterwards, each value is connected with one or multiple functional element(s) to validate whether and to what degree the expected value could be implemented under the support of the functional elements. ValueMapping is imported here for this purpose. If we go into the details of ServiceValue, the following four aspects must be elaborated: • ValueTaxonomy that describes information of service value classification. • ValueLifecycle that describes process and phases which a service value goes through before it is delivered to and consumed by its receivers. • DeliveryMeans that describes the temporal features of a value’s delivery to its receivers; • ValueIndicatorSet that describes a set of indicators to be used for measuring the implementation degree (quality and quantity) of the value.
202
Z.J. Wang, X.F. Xu, C. Ma and A. Liu
3.2. Service Value Taxonomy Values are co-produced by customers and providers together. No matter whether a value is tangible or intangible, it must lead to some improvements on specific aspects of its receivers. According to different types of improvements, we classify values into two categories, i.e., (a) ThingTransferingValue refers to those values generated by transferring some tangible or intangible “things” (e.g., information, a product, right of using a resource) from value producers to value receivers. Such values improve the possessions (of things) of the receivers. It is refined into 4 sub-categories: (a.1) Financial Value (FIV): monetary benefits transferred from value producers to value receivers; (a.2) Product Value (PRV): tangible products transferred from producers to receivers; (a.3) Information Value (INV): information transferred from producers to receivers; (a.4) Resource Usage Value (RUV): a resource’s “right to use” transferred from producers to receivers. (b) StateImprovementValue refers to those values generated by improving certain physical or spiritual states of participants. It is refined into 5 sub-categories: (b.1) Experience Value (EXV): the value receiver’s experience in engaging in specific services increases so that in the future he could provide higher-quality services which bring higher financial benefits to him. (b.2) Knowledge and Skill Value (KSV): the value receiver’s knowledge or professional skills in some specific domains are upgraded. (b.3) Market & Social Impact Value (MIV): the value receiver’s social impact in some social or marketing areas is expanded, e.g., increasing of market share, improvement of word of mouth. (b.4) (Thing’s) State Improvement Value (SIV): states of certain physical entities of the value receiver are changed by service activities like transporting, repairing, maintenance. (b.5) (People’s) Enjoyment Value (EJV): the physical or spiritual states of the value receiver are improved. ServiceValue ValueName ValueType ValueReceiver ValueProducer AttachedObject
INV
RUV
ValueTaxomony
+ValueType
ThingTransferingValue
StateImprovementValue
PRV
1
FIV
EXV
MIV
KSV
EJV
SIV
Fig. 2. Meta-model of service value taxonomy
When we model a value, we need to identify its name (attr: ValueName), type (attr: ValueType), producers (refers to the participant who generates the value, denoted as attr: ValueProducer), receivers (refers to the participant who obtains
Service Value Meta-model: An Engineering Viewpoint
203
and consumes the value, denoted as attr: ValueReceiver), and the object that the value is attached to, no matter whether the object is transferred from producers to receivers or the state of the object is improved (denoted as attr: AttachedObject). The meta-model concerning value taxonomy is shown in Fig. 2. 3.3. Service Value Lifecycle Most coarse-grained values cannot come into being all at once and need a comparatively long period during which they are gradually implemented. We call this the service value lifecycle (ValueLifecycle) [8] which is decomposed into 7 phases, i.e., (P1) BiLateralSearching. Before value co-production, a channel is to be established to connect unacquainted customers and providers together and form a “supply-demand” relationship between them. (P2) BiLateralNegotiation. In this phase, the customer contacts and negotiates with candidate providers and reaches a consensus on Service Level Agreement (SLA) of the expected values with specific providers. (P3) UniLateralPreparation. Before value co-production, some preparation work has to be done. For instance, the provider should prepare necessary resources, or he might contact other confederate service providers to outsource part of the service if he does not have sufficient capabilities to handle the service himself. (P4) CoProduction. This is the core phase of the value lifecycle. As all required participants have been specified and all necessary resources have been obtained, it is the time to “produce” the expected values by collaborations between both sides. (P5) Transferring. This is a simple phase in which produced values are transferred from providers to the customer. (P6) Usage. After the customer receives his expected value, he may further utilize the value in other services where the obtained value is to be transformed into other forms. (P7) Payment. The customer certainly needs to pay the providers for the value he gains. In this phase, money is transferred from the customer to the providers. Besides, the sequences (PhaseSequence) between one and other phases need to be modeled. In most services, all 7 phases exist and follow a specific sequence. Sometimes, there are exceptional circumstances, e.g., if a customer knows which providers are best suited to his requirements based on his historical experiences or “word of mouth”, he could directly contact the providers and come to an agreement, then P1 and P2 will be omitted. Another example is that sequences between P4, P5 and P6 are flexible, i.e., they may separate from each other (denoted as “4-5-6”) or may occur concurrently (e.g., “456”, “45-6”, “4-56”). P7 is independent of other phases and it may occur at any time during the service. We use three terms to model possible sequences, i.e., PhaseLockstep which refers that two phases occur in lockstep way, PhaseMerged which refers that two phases occur concurrently, and NoLimit which refers that there are no specific sequences between two phases. As each phase has distinct contributions to value implementation, there are distinct value indicators attached to each phase. To improve the value produced, service designers look for innovative design decisions in each phase to improve the corresponding indicators as far as possible.
204
Z.J. Wang, X.F. Xu, C. Ma and A. Liu
The meta-model of service value lifecycle is shown in Fig. 3. PhaseMerge ServiceValue NoLimit
ValueIndicatorSet
PhaseLockstep
1
1
ValueLifecycle
PhaseSequence
ValueIndicator +Indicators 1
1..7
1..n
1
Usage
Phase
BiLateralSearching
Payment BiLateralNegotiation
Transferring
UniLateralPreparation
CoProduction
Fig. 3. Meta-model of service value lifecycle
3.4. Means of Value Delivery Value lifecycle describes the steps for how a value is produced and transferred from nonexistence to be created for consumption. If we examine the transferring phase (P5) according to the time, period and frequency of the transfer, different values follow one of the following means of delivery, i.e., (1) Time-Discrete Delivery (TDD) [9]. This takes place at one instant of time of zero duration and stops at the point in time when they are started. When value is modeled, the concrete time spot (attr: Time) that the transfer occurs is central to our concern. (2) Time-Continuous Delivery (TCD) [9]. This takes place over a period of time and stops some time after they are started. Delivery duration (attr: Duration) is used to state how long a delivery takes place. TDD Time
ServiceValue
1
TCD Duration
TPD Frequency
DeliveryMeans
TAD
Fig. 4. Meta-model of value delivery means
(3) Time-Periodical Delivery (TPD). Value is transferred periodically and repeatedly from one side to another through either time-discrete or time-continuous delivery. Delivery frequency (attr: Frequency) is used to state how many times delivery occurs in the time-extent of a business case.
Service Value Meta-model: An Engineering Viewpoint 205
(4) Time-Accumulative Delivery (TAD). There is a particular type of situation in which, during each value delivery, the value is too small to be explicitly observed and perceived; however, after some period in which value is delivered multiple times, the total accumulative value becomes apparent. Note that a TPD must contain a set of TDD or TCD and a TAD is a specialized TPD. Fig. 4. shows the meta-model of value delivery means. 3.5. Service Value Indicator A set of value indicators are attached to each value to measure the value’s implementation degree. In economics, value is measured by the ratio of benefit to cost. Aiming at broad-sense values, benefit-oriented indicators and cost-oriented indicators are to be adopted similarly, called Value Benefit Indicators (BenefitIndicator) and Value Cost Indicators (CostIndicator). The former measures the benefit the value brings to its receivers, i.e., (1) to which degree AttachedObject transferred to the receivers is good enough; or (2) to which degree the state of AttachedObject is improved. The latter measures the cost paid to obtain the value, including monetary cost, time and energy cost, resource usage cost, etc. An indicator may have a continuous or discrete data type (attr: IndicatorType). Its concrete value (attr: Value) results from calculation or reasoning according to the QoS of functional elements to which the value is connected. ServiceValue
1
ValueIndicatorSet
BenefitIndicator ValueIndicator IndicatorType Value Scope
Discrete IndicatorType
CostIndicator
Continuous
Fig. 5. Meta-model of value indicator
3.6. Service Value Relationship A value does not exist independently but there are close relationships between different values. Such relations lead to the dependency between the implementation degrees of different values. When a service system is designed, it is necessary to look for a tradeoff between interdependent values to ensure that both are to be implemented to an acceptable level. There are 5 primary types of value relations: 1) Composition. To realize a coarse-grained value, multiple diverse finegrained values are to be implemented separately and they are further composed together to form large and significant values. A “whole-part” relationship is formed. Concerning the relative necessity that the part has to the whole, there are
206
Z.J. Wang, X.F. Xu, C. Ma and A. Liu
four possibilities, i.e., Mandatory, Optional, SingleSelection, and MultipleSelection. 2) Aggregation. This is similar to Composition but the coarse-grained value is a combination of multiple homogeneous fine-grained values. Attribute Scale is used to describe what and how many find-grained values are to be merged together. 3) TemporalAssociation. It means the delivery of values should follows strict sequences, i.e., some values are prerequisite of other values. 4) ProducerAssociation. Two values must be provided by the same producers (ProducerEqual) or must have different producers (ProducerInequal). 5) Dependency. Implementation degrees of multiple values are not completely independent of one another, i.e., improvement of one value will possibly lead to improvement or deterioration of another value. Denote DD(vi ; vj) as the dependency degree (DependencyDegree) that vj depends on vi. Value dependency is classified into positive dependency (PositiveDependency) (i.e., improvement on vi will lead to improvement on vj) and negative dependency (NegativeDependency) (i.e., improvement on vi will lead to deterioration on vj). ProducerEqual ProducerAssociation
1
ServiceValue
ProducerInequal 1..n
ValueRelation
TemporalAssocation Mandatory
PositiveDependency Optional Composition SingleSelection
MultipleSelection
Merge Scale
DependencyDegree
Dependency NegativeDependency
DependencyFunction
Fig. 6. Meta-model of value relations
3.7. Mapping between Value and Functional Elements The last but most crucial aspect that must be described is the mapping between value and functional elements. For each value, there are one or multiple behaviors, resources, information, etc that facilitate the implementation of the value. Each indicator of the value may be calculated or reasoned by the QoS of the corresponding functional elements. Therefore, we describe the mappings from two aspects: 1) mapping between value and functional elements (ValueMapping); 2) mapping between value indicators and the QoS of the functional elements (ValueIndicatorMapping). Concerning ValueMapping, designers identify mappings based on the object attached to the value, i.e., to check whether each functional element has contributions to the transfer or state improvement of the object. If YES, then there are mappings between them. The next step is to identify the element’s contribution
Service Value Meta-model: An Engineering Viewpoint 207
to the implementation of the value, i.e., which phase(s) it contributes to the value’s lifecycle. There are 3 types of ValueMapping: 1) 1:1, i.e., one value is related to only one functional element; 2) 1:n, i.e., one value is related to multiple functional elements; 3) Global mapping, i.e., a value cannot be directly mapped to any concrete elements but is related to the whole service. The process of establishing ValueMapping and ValueIndicatorMapping is called “Value Annotation”. 1:1
1:N
Global
Resource
MappingType
Information 1..n
ServiceValue 1
ValueMapping MappingType
1..n
FunctionalElement
1
Participant 1..n
1..n
ValueIndicator 1
1..n
ValueIndicatorMapping
QoS
Behavior
1
Fig. 7. Meta-model of Mapping between Value and Functional Elements
4. Service Value Modeling and Analysis Based on the value meta-model, we have designed a multi-level service value model which is composed of four layers: Service Proposition Model (SPM), Participant-Oriented Value Network (POVN), Value Dependency Model (VDM), and Value Annotation Model (VAM). Based on this value model, a value-aware service engineering and methodology (VASEM) is put forward. In VASEM, service values are considered as the ultimate optimization goals and need to be aware in every step of service system design and development. Firstly, value models are established. Then the identified values are connected with functional elements of service models (called “value annotation”). Based on the annotation, service models are qualitatively and quantitatively analyzed to validate whether and to what degree all expected values could be realized. If there are deficiencies, service model are to be optimized by adjusting the selection of functional elements and their relationships. If these value deficiencies cannot be overcome by model optimization, this means that the value constraints are too strict (i.e., value expectations are too high to be satisfied), then they are fed back to value models for further adjustment. If no value deficiencies are found during the analyses, then the service system is to be designed based on the service models.
208
Z.J. Wang, X.F. Xu, C. Ma and A. Liu
Due to limited space, details of values models and VASME may be found in [10] and [11].
5. Conclusions Traditional viewpoints of service value usually focus on financial or economic meanings. Existing work such as the Value Network are commonly adopted to analyze service at the business level. Compared with existing works, the metamodel presented in this paper pays greater attention to describing service values from a service engineering point of view. Its main purpose is to support better design and development of service systems to ensure they will deliver expected values to customers and providers. To describe the values is only one of the initial steps of value-aware service engineering and methodology. Future work includes: (1) To look for a uniform set of value indicators for each type of service values and corresponding measurements; (2) to develop an automatic value annotation method; and (3) to exploit the value-oriented service model analysis method.
6. Acknowledgement Research works in this paper are supported by the National Natural Science Foundation (NSF) of China (60803091, 70971029) and IBM-HIT Joint Lab 2009 Joint Research Project (No.JLAS200907001-1).
7. References [1] [2] [3] [4] [5] [6] [7] [8] [9]
Tien J, Berg D, (2003) Towards Service Systems Engineering. IEEE International Conference on Systems, Man and Cybernetics, 5(5):4890–4895 Spohrer J, Maglio P, Bailey J, Gruhl D, (2007) Steps towards a Science of Service Systems. IEEE Computer, 40(1):71–77 OMG, (2007) Business Process Modeling Notation (BPMN). http://www.bpmn.org Henkel M, Perjons E, Zdravkovic J, et al, (2006) A Value-based Foundation for Service Modelling. The 4th European Conference on Web Services, Washington DC, USA: IEEE Computer Society Press, 129–137 Allee V, (2000) Reconfiguring the Value Network. Journal of Business Strategy, 21(4):36–39 Gordijn J, Yu E, van der Raadt B, (2006) e-Service Design Using i* and e3value Modeling. IEEE Software, 23(3):26–33 IBM Corporation (2007). SSME: Systems. http://www304.ibm.com/jct09002c/university/ scholars/skills/ssme/resources.html. Wang ZJ, Xu XF, (2009) SVLC: Service Value Life Cycle Model. IEEE International Conference on Cloud Computing, IEEE Computer Society, 159–166 Wieringa R, Pijpers V, Bodenstaff L, Gordijn J, (2008) Value-driven coordination process design using physical delivery models. 27th International Conference on Conceptual Modeling, Lecture Notes in Computer Science 5231, Springer, 216–231
Service Value Meta-model: An Engineering Viewpoint 209 [10] Wang ZJ, Xu XF, (2009a) Multi-Level Graphical Service Value Modeling Method. Computer Integrated Manufacturing Systems, 2009, 15(12): 2319–2327 [11] Xu XF, Wang ZJ, (2008) Value-Aware Service Model Driven Architecture and Methodology. Invited paper on Service Science Cross Session of the 20th World Computer Congress, Springer Boston, 280:277–286
Part IV
Architectures and Frameworks for Interoperability
An Interoperable Enterprise Architecture to Support Decentralized Collaborative Planning Processes in Supply Chain Networks Jorge E. Hernández1, Raul Poler1 and Josefa Mula1 1
CIGIP (Research Centre on Production Management and Engineering). Universidad Politécnica de Valencia. Escuela Politécnica Superior de Alcoy. Edificio Ferrándiz y Carbonell, 2, 03801 Alcoy (Alicante), Spain. {jeh, rpoler, fmula}@cigip.upv.es
Abstract. Supply chain management, since many years, has been realated to coordinate the efforts among the supply chain nodes in order to mitigate unpredictable behaviours related to environment uncertainty. This allows to the involded nodes to achieve common goals in a efectivelly maner likewise the customers demand. Thus, by sharing accurate and actionable information, on a timely basis, the collaboration among the nodes will emerge in order to improve the decision-making process related, mainly, to the planning processes in the supply chain. Hence, from a decentralized perspective, each supply chain node will consider their own enterprise systems in order to manage and exchange the right information among them. Thereafter, aspects such us the interoperabilty of the systems are a very crytical issue to be considered, even in the modelling process and also in the implementation stage. Then, this paper, supported by the Zachman framework and by the REA standar ontology, proposes an novel interoperable enterprise architecture to support the decentralized collaborative planning and the decision-making processes in the supply chains. In addition, the proposed architecture consider a multi-agent based system approach as well as its application to a real automobile supply chain network. Keywords: Enterprise architecture, Interoperability, Multi-Agent, Collaborative planning
1. Introduction The supply chain (SC) management process encompasses all the necessary activities to satisfy final customer demand by considering, in the most of the cases, the distribution of components and raw materials among SC nodes and also how they interact to coordinate their activities and decision-making process. In fact, [3] emphasize how the main information elements to be considered in the SC management process must cover node actions (orders, order filling, shipping, receiving, production, etc.), node policies (inputs and outputs inventory policies),
214
J. E. Hernández, R. Poler and J. Mula
and the costs and rates involved. Therefore a collaborative process will emerge by sharing the proper information among the SC nodes. In addition, collaboration in SCs is important in terms of innovation as every node realize the benefits related to the high quality, lower costs, more timely deliveries, efficient operations and the effective coordination of activities [21]. Moreover, and from a descentralized point of view, collaborative planning (among SC partners) can be achieved by a simple form of coordination of upstream planning by providing the collaboration partners an opportunity to modify suggested order/supply patterns iteratively [7]. Thus, the collaborative relationships change the way in how the business are doing in SC’s, in this context it is possible to say that nodes trends to evolve from cooperation to collaboration [18]. In order to support this, and by considering the fact that enterprise engineering has been leveraged as key topics in enterprise management [17], the concept of enterprise architecture emerges as a system to support the integration of the main concepts, information and processes related to the SC. Thus, as defined by [25] the