Key words: IT Service Management, ITIL, Semantic technologies, Ontologies Martin SARNOVSKY*, Karol FURDIK**, Martin TOMASEK** APPLICATION OF KNOWLEDGE MANAGEMENT AND SEMANTIC TECHNOLOGIES IN IT SERVICE MANAGEMENT The paper is focused on research perspectives of approaches and solutions in the IT service management (ITSM). The ITIL best practices and ISO/IEC 20000 standard are nowadays the worldleading conceptions of managing IT services in enterprises. Together with the principles of Semantic Web, knowledge technologies and service-oriented architectures, the standardized ITSM can provide a framework for designing and maintaining interoperable service-based applications. This innovative research stream was already emphasized by the European Commission in the 7th Framework Programme, ICT Challenge 1: Pervasive and Trustworthy Network and Service Infrastructures. The FP7 ICT project SPIKE (Secure Process-oriented Integrative Service Infrastructure for Networked Enterprises, http://www.spike-project.eu), aiming at the ICT support for creating short-term and projectoriented organizational alliances of networked enterprises, is described in the paper as a reference application case of integrating ITSM with semantic and knowledge representation technologies. The approach presented in this paper includes business process modeling, design and development of ontology structures supporting the ITSM processes and semantic annotation of web services organized into process workflows. Our main focus was to introduce the idea of leveraging semantic technologies for support of configuration database management process and to enhance management processes in ITSM by providing collaboration environment for ITSM processes. Presented paper describes such approach and discusses future work including the implementation and planned testing environment. * Technical University of Košice, Faculty of Electrical Engineering and Informatics, Department of Cybernetics and Artificial Intelligence, Letná 9, 042 00 Košice, Slovakia. ** Intersoft, a.s., Floriánska 19, 040 01 Košice, Slovakia.
1. INTRODUCTION Service-oriented Architecture (SOA) and solutions based on services gained signifycant amount of interest in computer science research and nowadays represent the popular and widely spread technologies used. Web services have been emerging as the lead implementation of SOA upon the Web. On the other hand Semantic Web provides a common framework that allows data to be shared and reused across application, enterprise, and community boundaries. Semantic Web services then allows extension of web services with semantic information providing the mechanisms for invocation or functionality reasoning. Utilizing the principles of Semantic Web, SOA and knowledge technologies with the standardized IT service management can provide a framework for designing and maintaining interoperable service-based applications. Main aim of presented paper is to present the conceptual framework for developing a semantic model of ITIL -one of the selected ITSM frameworks. 2. ITIL AND IT SERVICE MANAGEMENT To precisely define what a service management is, it is needed to specify what the service is, more concrete, what is the IT service. According to [14] a service is a means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific risks and costs. This definition of service is rather general. Speaking of IT services we will consider the services that in some way facilitate ICT technologies to its use. Then, a simple example of IT service and customer outcome satisfied by this service can be: Customer outcome: Sales people spending more time interacting with customers facilitated by service: Remote access service that enables reliable access to corporate sales systems from sales people s laptops To ensure, that the IT services satisfies the customer s needs and to use corresponding ICT technologies effectively, these have to be put under specialized management processes. This discipline is called Service Management, and it is a set of specialized organizational capabilities for providing value to customers in the form of service. IT Service Management evolved during the time into the highly standardized frameworks based on best practices. Best practices evolved into the industry standards for
management of ICT (ISO/IEC20000) and also into the public domain frameworks such as ITIL, or CoBiT. In the next section we briefly describe one of them ITIL. 2.1. ITIL ITIL (IT Infrastructure Library) is a framework that describes best practices in the IT service management. Library is public and nowadays, in its third version, consists of 5 core publications. Office of Government Commerce (OGC) published initial version of ITIL in 1989 in Great Britain. It has been revised into the more connected and consistent ITIL V2 and in 2007 it was enhanced and released as ITIL V3. Fig. 1. IT service lifecycle ITIL V3 consists of 5 core books that cover the whole lifecycle of the service. Different stages of service lifecycle are depicted on fig. 1. The figure shows each stage of the lifecycle from initiation from requirements from business. Its main stages are also connected to ITIL core publications. Basically it shows, that all activities and processes
are business driven, its initial definition and analysis is covered by Service Strategy and Service Design stages. Service Transition describes the migration into the live environment and Service Operation and Continual Service Improvement publications describe the real operation of the services in business. Implementation of the service lifecycle enables seamless integration into the business processes as well as ability to control and manage the services from initial requirements until the service is operative. Service Strategy focuses on helping the organizations improve over the long term. It covers some key topics including the service value definition, business case development, service assets, market analysis and also defines corresponding processes for management of assets, service portfolio, finances. Service Design aims more specifically on designing of IT services and processes. In ITIL sense Service Design means to consider all elements that can be relevant to technology service delivery. Service Transition covers the area between design of service and its transition into the operational use and describes the corresponding processes (Change Management, Release Management, Service validation, testing etc.). Service Operation is the part of the lifecycle, where the services are actually deployed and are in operational use. It covers wide range of processes and functions including the monitoring of the services and problems and management between the service reliability and its costs. 3. ITSM AND SEMANTICS STATE OF THE ART The idea of semantically enhanced ITSM was invoked by general principles of Semantic Web [2], especially when they were applied on SOA-based solutions. Such applications are usually designed as compositions of services and sub-processes orchestrated into a workflow structure. The management of services in this type of applications is ensured by defined workflow sequences, which are formalized as abstract and executable business processes [12]. Managing IT services thus means designing properly the corresponding business process models for desired service workflow. Actually, the modeling of abstract business processes is tightly related to the Service Strategy and Service Design phases defined in ITIL, while the design of executable processes corresponds to the Service Transition phase of ITIL. Moreover, to assure the service interoperability and data mediation, the services in the workflow can be semantically described by means of a shared knowledge model (ontology), which provides a common vocabulary for information exchanged between possibly heterogeneous services. This feature is especially important for ITIL phases
of Service Operation and Continual Service Improvement, since it enables seamless communication between services according to the meaning of input and output values, dynamic discovery and selection of services in a running workflow, as well as a relatively easy replacement of a service with an alternative service. The advanced technology of these so-called Semantic Web services [15] is quite frequently used nowadays and is supported by semantic frameworks such as OWL or WSMO. In a combination with business process modeling, the Semantic Web services should be capable to serve as a methodological and technological platform for developing modular service-based solutions in line with all the phases and processes of ITSM. The vision of semantic business process modeling was formulated in [8] and was further elaborated in numerous research initiatives such as, for example, the Object Management Group (http://www.omg.org), European FP6 R&D projects STASIS (http://www.stasis-project.net), OPUCE (http://www.opuce.tid.es), or SUPER (http://www.ip-super.org). Namely the project SUPER is probably the most comprehensive attempt towards the implementation of semantic business process modeling environment [1]. The aim of this project was to achieve a higher degree of automation in discovery and mediation of co-operating services. The use of semantic technologies as Semantic Web services in the process modeling, service configuration, execution, monitoring, and analysis is envisioned as a method that can overcome the heterogeneity and incompatibility problems towards the semantically interoperable services. It may also help to reduce the human intervention throughout the lifecycle of business process modeling [10]. However, in the project SUPER as well as in other mentioned research activities there is no direct and explicit support for ITIL phases. It means that, to be applied in practice in the environment of IT enterprises, the proposed solutions of semantic process models need to be mapped into ITIL best practices or standardized ISO/IEC 20000 requirements. On the other hand side, there exists a wide variety of commercial as well as open source tools supporting all the ITIL phases and the respective processes. These tools are regularly evaluated and compared on well-known web portal of Pink Elephant (http://www.pinkelephant.com). However, focus of these tools is solely on ITIL and a support of semantically enhanced services or processes is lacking. It seems that there is a gap between the enterprise practice, which is focused mostly on ITIL and related standards, and the research community trying to investigate in the area of Semantic Web. There are some attempts to overcome this gap, for example [13]; in general, however, it can be stated that the research and development in modeling ITIL practices by semantics is still in its beginning.
4. INTEROPERABILITY OF WEB SERVICES THE SPIKE APPROACH The semantic-based integration of IT services, organized into a structure of predefined business processes, is in focus of EU FP7 project SPIKE (http://www.spikeproject.eu). This project is aiming at the development of a platform for secure, open and flexible collaboration of enterprises in short-term project-oriented business alliances. The SPIKE platform was designed as a market place that enables contracting, invoking, execution and monitoring of services provided and consumed by the business alliance members. The services are organized into the pre-defined value chain, which is specified by a workflow of sub-processes and tasks grounded in the services of several types web services, electronic on-line services, or tasks performed by human actors. Interoperability of these heterogeneous services is achieved by semantic extensions over the formalized WSDL service description. Architecture of the SPIKE system, described in [11], is based on semantically enhanced enterprise service bus [3, 9], which serves as the main communication component for handling the messaging and data exchange between individual parts of the SPIKE infrastructure. It uses semantic description of service capabilities, properties, and exchanged information artifacts, enabling automated service discovery, routing, composition and data mediation. This way, the service bus connects the main functional modules of the infrastructure, namely: System Core, a back-end for processing services and all the system data, Portal Instance, a graphical user interface of the platform, and Administration Subsystem, a toolkit for overall system maintenance, monitoring and reporting. The solution is based on technologies of Intalio Tempo (http://tempo.intalio.org) and WSMO framework (http://www.wsmo.org) employed for visualization and modeling of semantic business processes, while the execution environment for processes is built on Java Business Integration specification JSR 208 [6]. The SPIKE platform development is primarily focused on three pilot applications in business organizations from Austria and Finland. Austrian pilots include the application cases (ACs) of Business Alliances and Identity Federations, which are focused on specific sub-processes of integrating services into business alliances and granting a secure access to them. The Finnish AC, named as Documentation Management, covers whole process of establishing and maintaining a collaborative environment business for the value chain of providing services by means of secure knowledge and content management.
4.1. SPIKE AND ITIL The overall SPIKE platform integrates external services into the process workflow and thus it can be aligned with an application of IT service management. Indeed, all the phases of ITIL can be identified during the setup and maintenance of business collaboration. The Service Strategy is applied during the specification of value chain, where is important to ensure its compatibility with business goals of providing organization. Creation of business process models for the given value chain, definition of tasks organized into workflow structures, as well as grounding of tasks on concrete services is related to the Service Design phase of ITIL. The specified set of external services, including alternative or candidate services for some of tasks, can be considered as the service portfolio, which is the most important system in the Service Design phase [14]. The Service Transition phase corresponds in SPIKE to the process of establishing a business alliance for defined process model. The services are contracted on agreed level of quality, processes of change management, configuration management and release management are specified. This phase also includes a proper distribution of identities, access rights and credentials for all dedicated alliance members, consumers of contracted services, which allows accessing internal applications and resources on the side of alliance members in the role of service providers. The way of providing such identities, as it is applied in SPIKE pilot application of Identity Federations for setting up the collaboration within an established business alliance, is schematically depicted in fig. 2. On the side of SPIKE system, the process is supported by the resource and role management, which contains the portfolio of contracted services together with all the information required for using the services by an authorized service requester. Fig. 2. Schema of the collaboration setup process in SPIKE
The run time of the executable workflow, generated from the designed business process models of a business alliance, is related to the Service Operation phase of ITIL. Besides standard ITIL processes such as incident and problem management, it also includes the processes of adjusting the collaboration by extending or reducing the number of alliance partners or provided services. All these operations are supported by components of SPIKE System Core module, which are responsible for maintaining services, processes, and whole alliance [11]. Running workflow is visualized and can be traced in the SPIKE Portal Instance module. Finally, the ITIL phase of Continual Service Improvement is related to the performance evaluation and monitoring of executed services. This functionality is provided by the components of SPIKE Administration Subsystem. 4.2. SEMANTIC STRUCTURES SUPPORTING ITSM IN SPIKE The SPIKE system employs semantics in phases of design and operation of services. Since the solution is based on semantically enhanced Web services, the WSMO platform was adopted as the main framework for implementing all the underlying semantic structures. Value chains and workflow sequences for an alliance are defined as abstract business process models and are formalized in WSMO-compatible BPMO notation [1]. Fig. 3. BPMO model of the service ordering sub-process
For example, a BPMO model of the sub-process of ordering and contracting services is presented in fig. 3. This use case, which is a core of the Legacy Applications AC, is modeled as an interaction between three actors Service requestor, Service provider, and the SPIKE platform. The Service requestor searches for a proper service (by the Service Search sub-process, which is modeled in a separate use case) and prepares an order for the retrieved service that matches with his/her business needs. Afterwards, the order is processed by the SPIKE platform. The Service provider is notified; the contract of usage is generated and forwarded to the requestor. After accepting the contract the service is ready for usage. Optionally, the requestor may negotiate the contract details with the Service provider. Abstract business process models for all use cases of SPIKE pilot applications were created in a similar way and are accessible under a single root location of http://www.spike-project.eu/bpmodels/. Tasks in these process models can then be grounded to concrete services expressed in WSDL format. To ensure the interoperability of services in the process workflow, the service parameters (i.e. inputs, outputs, capabilities, etc.) need to be described by additional semantic structures ontology concepts. For example, the process in fig. 3 requires, according to the ITIL specification, a formal contract on desired quality of provided service, together with precise conditions of the service usage. Such a contract, known as Service Level Agreement (SLA), is a document that contains specific and obligatory fields such as service scope, availability, reliability, customer support, performance, charging, responsibility, etc. These parameters of SLA can be specified as concepts in a shared SPIKE ontology and then may be used as semantic extensions of services dealing with formalized service contracts. In SPIKE, the SA-WSDL format of service annotation [5], WSML ontology format, and WSMO Studio toolkit [4] are employed for these purposes. The structure of SPIKE ontologies, designed by analyzing the descriptions and requirements of user partners and by reusing already existing ontology resources [7] was specified in three logical groups [6]. Process-related ontologies provide conceptual models for semantic description of business processes and their elements such as Process, Task, Service, etc. System-related ontologies semantically describe the platform environment, including concepts for role and resource management, collaboration settings, service contracts, etc. Domain ontologies extend the general semantic structure of process-related and system-related ontologies towards the SPIKE pilot applications. All the ontologies are implemented in WSML formalism and are freely available for further use at http://www.spike-project.eu/ontologies/.
5. CONCLUSIONS, FUTURE WORK The described approach of integrating services into workflow structures by means of semantic structures indicates tight relationship with the IT service management principles and standards. It is, however, necessary to state that the presented SPIKE solution, at least in its first prototype finished in winter 2009, was not built primarily upon ITIL specification. Contrary, the testing of the first SPIKE prototype showed a necessity to adapt the ITSM processes modeled in SPIKE according to the ITIL best practices or ISO/IEC 20000 standards. It is especially important for ensuring wider acceptance and reliability of SOA solutions of SPIKE-like type. Similarly, semantic structures supporting the shift of SOA solutions towards Semantic Web should be constructed with full respect to ITIL. The SPIKE ontologies developed for the first prototype of the platform do not precisely reflect ITIL concepts, namely in the management of incidents, problems, capacities and configurations. However, due to the complexity of ITIL, its semantic modeling is rather difficult and longlasting task. A suitable approach could be to divide the ITIL into relatively independent parts such as particular phases and processes, which can be expressed by respective structures of ontologies and process models. At the Technical University of Košice, in the scope of Business Informatics field of study and in a co-operation with itsmf Slovakia (http://www.itsmf.sk), we have defined a series of themes for diploma thesis for designing and developing the semantic structures of ITIL parts. It includes, for example, ontologies and process models for service design, service operation, configuration management, capacity management and incident / problem management. In parallel, the semantic structures will be employed and tested in the second half of 2010 on finalized SPIKE platform, which will be used as a reference application for created models and ontologies. ACKNOWLEDGEMENTS The SPIKE project is co-funded by the European Commission within the contract No. FP7-ICT-217098 (50%). The presented work is the result of the project implementation: Development of the Center of Information and Communication Technologies for Knowledge Systems (ITMS project code: 26220120030) supported by the Research & Development Operational Program funded by the ERDF (50%).
REFERENCES [1] BELECHEANU, R. et al, Deliverable 1.1: Business Process Ontology Framework, Project IST 026850 SUPER, Public Deliverable, 2007. [2] BERNERS-LEE, T., HENDLER, J., LASSILA, O., The Semantic Web, Scientific American, 2001. [3] CHAPPELL, D. A., Enterprise Service Bus, Sebastopol, CA, O'Reilly Media, Inc., 2004. [4] DIMITROV, M. et al, WSMO Studio Users Guide, Ontotext Lab., 2007, http://www.wsmostudio.org/doc/wsmo-studio-ug.pdf. [5] FARRELL, J., LAUSEN, H., Semantic Annotations for WSDL and XML Schema, W3C Recommendation, 28 August 2007, http://www.w3.org/tr/sawsdl/. [6] FURDÍK, K., Semantic annotation of services and processes in business alliances, Process Control 2010, 9th international conference, June 7-10, 2010, Kouty nad Desnou, Summaries Volume, University of Pardubice, Czech Republic, 2010, 42 (full paper on CD). [7] FURDÍK, K., MACH, M., SABOL, T., Towards semantic modelling of business processes for networked enterprises, Proc. of EC-Web 2009, Linz, Austria, Springer Berlin / Heidelberg, LNCS 5692, 2009, 96-107. [8] HEPP, M. et al, Semantic Business Process Management: A Vision Towards Using Semantic Web Services for Business Process Management, Proc. of the IEEE ICEBE 2005, October 18-20, Beijing, China, 2005, 535-540. [9] KARASTOYANOVA, D. et al, Semantic Service Bus: Architecture and Implementation of a Next Generation Middleware, Proc. of the 2nd International Workshop on Services Engineering (SEIW) 2007, ICDE Workshops, IEEE, 2007, 347-354. [10] KARASTOYANOVA, D. et al, A Reference Architecture for Semantic Business Process Management Systems, Multikonferenz Wirtschaftsinformatik 2008, Berlin, GITO-Verlag, 2008, 1727-1738. [11] MACH, M., BEDNÁR, P., FURDÍK, K., Support for Forming Temporal Business Alliances as Networked Enterprises, Proc. of CECIIS 2009, Varaždin, Croatia, University of Zagreb, Faculty of Organisation and Informatics, 2009, 179-186. [12] OUYANG, Ch. et al, From BPMN Process Models to BPEL Web Services, Proc. of International Conference on Web Services (ICWS '06), Chicago, IL, 2006, 285-292. [13] SHANGGUAN, Z., GAO, Z., ZHU, K., Ontology-Based Process Modeling Using etom and ITIL, IFIP International Federation for Information Processing, Research and Practical Issues of Enterprise Information Systems II, Springer Boston, LNCS 255, 2008, 1001-1010. [14] TAYLOR, S., LLOYD, V., RUDD, C., ITIL - Service Design, London, TSO, 2007. [15] W3C Semantic Web Services Interest Group, http://www.w3.org/2002/ws/swsig/.